config: do not resolve a pinned version through newer schemas
version_chain() consulted a version's ancestors and then its
descendants, so a key the selected version did not define resolved to
the value a newer schema introduced it with. A configuration pinned to
an old version then changes behaviour whenever a newer schema adds an
option, which is what pinning is meant to prevent.
Resolve a version through itself and its ancestors only, and drop
next_version(), which only the descendant walk used. Every key the code
reads must now be defined in the oldest schema; version 1 gained the
two it was missing in the previous commit, and test_builtin_versions()
already fails if any version cannot resolve a key another version
defines.
Update the version_chain(), config.version and --show-builtin-config
descriptions to match, and say in the version 1 file comment that new
options get a key there too, at the value that keeps v0.11 behaviour.