Item12952: Revert change to AdminGroup.

We don't ship a populated AdminGroup
Item12952: Checker for ConfigureFilter

Try to make it more obvious that a user is going to lock themselves out
from configure.
Item12952: Refactor bootstrap, load, & save

This fixes the issue that "discovered" extension modules are not saved
into the configuration.   The issue is that the Save process clears and
applies posted changes to the new configuration,  but values quietly
added to $Foswiki::cfg by the Configure::Pluggables:: are lost.

 - Eliminate the "NOT_SET" convention.  Bootstrap should really set
   everything that's needed, or die trying.  This was SMELL anyway.
 - Refactor bootstrap out from Foswiki.pm into Configure::Load.  All
   methods of loading a configuration are in the same module now.  And
   the TestBootstrapPlugin will be able to drive the "real thing".
 - Unify save/restore of "BOOTSTRAP" variables, be they set during the
   actual bootstrap process, or by the "Pluggables" bootstrapping of
   newly installed extensions.   This simplifies the save code as well.

There is still a major bug related to extension discovery.
Configure::Pluggables::PLUGINS creates the {Plugins}{<plugin>}{Enabled}
but it does not merge in the Config.spec defaults for all the other plugin
settings.

I can't really fix it becuase I'm not sure if the original intention is
that the Config.spec be loaded in Pluggables::PLUGINS.   I suspect that
the jsonrpc  "getcfg" function should be called to load in all the
defaults. Currently only getspec is called to load the key definitions
and not their values.

This commit doesn't impact this either way.  Extensions installed before
the first run of Configure are configured correctly.  Extensions
installed after LocalSite.cfg exists don't get their default
configuration merged.