config: separate frozen version aliases from tracking ones
The alias table maps every name to a version string, which makes two
quite different kinds of name look identical at the point of use.
STABLE and CURRENT resolve through build constants, so what they name
changes when a constant is bumped; v0.11 names one fixed schema and will
go on naming it however far development moves ahead.
That difference does not matter while a name is only ever a choice a
person makes in a config file. It starts to matter as soon as a name can
be stored in structure that outlives the build that read it -- a schema's
inheritance edge, for one, where an edge written as CURRENT would
silently re-parent itself when the constant moved, and become a self-edge
once CURRENT reached that schema.
Record the distinction in the table rather than leaving it to be
rediscovered. No behaviour changes.