It warrants more explanation than is reasonable
in the midst of the rest of the rules,
and allows it to be included in alternative locations
without unnecessary code duplication.

There was previously support to allow personal repository creation,
but whether you could access those repositories was still limited to ownership.

This allows you to expand rules so that even if a repository
was owned by someone else you could still read it if it's in your prefix.

In most circumstances this should not matter,
but it can cause confusing error messages
if you are told you are denied read access to a repository in your prefix
if it instead doesn't exist, since the ownership test requires it to exist.

We can't instead report that the repository doesn't exist before checking owner
since that would leak that a repository you don't have access to exists.

This adds lace interfaces for the keyring command, a basic
keyring command with list, create, destroy, and a yarn for it,
along with some defines in the skel ready for user rules.

This changes the default rules to make it request variables from clod directly,
so that we're definitely testing config from clod.

Allow users to change their own password

Adds op_set_readme to the defines in the skeleton ruleset.  This also adds
op_set_readme to op_is_config since the README is essentially configuration for
the project.  Projects can perform deeper checks themselves if they wish, but
the global ruleset applies the same to README changes as to everything else to
do with project configuration.