Our only user of this at the moment is teken.{fg,bg}_color. These are
special because teken is a library common to both the kernel and the loader,
and we want to avoid having special vars to control the loader vs. the
kernel. Ideally, if a user wants a different set of console colors, then
they set the appropriate teken variable and it Just Works(TM) everywher.
We can't just avoid setting the env vars, because we specifically want to
install a hook to adjust how loader is drawn.
This allows us to avoid breaking a kernel config(5) that has some default
teken colors set with our defaults. That's a valid configuration, even if
it might seem weird that they don't want to set colors in both loader and
the kernel -- they may not anticipate spending any time in loader, and thus
prefer to just let it do its default behavior.
NOKENV is expected to be unset if the value is overwritten, rather than
acting as a persistent marker that we do not want the value to persist under
any circumstance. We can always add another flag bit later for persistence
if we find a use for that, but most variables are fine to carry over. This
is mostly needed for environment variables that we really just want to set
a hook for.