Fixed problem with Context's not properly initializing themselves with
the WW environment parameters (like zeroLevelTol and useBaseTenLog).
The copy method and the method that did an initialized copy used to be
separate routines, but that turned out to be unnecessary, so they have
now been merged (copy always tries to initialize the WW values when it
can, and when the copied context doesn't already have them).
The reason this is complicated is that a number contexts are set up
before the global.conf data is available, so these can't be
initialized with the WW values. Also, these default contexts are
stored in the persistant processes, and we don't want to leave
possibly course-specific values lying around in them, so whenever a
context is selected, it is copied from the standard version and the
WW parameters are inserted into it. The problem author can only
modify the copy, not the original, so this is OK with mod_perl.
The context's copy method now always tries to initialize (we used to
have to call initCoopy to get a copy that has the WW parameters
inserted). That turned out to cause trouble with code that handled
contexts without the usual Context() command.