Fixes some tests 2

This was discussed extensively before and my stance was always, it's okay to have tests that require config. customization by default.  The problem I keep running into regarding this relates to runs in a restricted environment.  In this case (which is more common than you'd think), it's better to have these tests fail with "you forgot to configure it!" than some strange connection timeout error, or whatever else would/could result.

In other words, part of setting up a test environment is going through all the configs and specifying what is needed.  If there are items like these w/ values filled it, it's super-duper easy to overlook them and miss the mistake for a long time.  I wouldn't make such a big deal about it, except I've actually run into this exact problem with our tests several times (internal test environment).

**HOWEVER** I also don't want to force "not fixing a problem", so perhaps there's an alternate way to address this?  One idea I saw used (somewhere) was to have a special ``__WARNING__`` option.  When present, it's taken as a signal that the defaults were not modified, causing the test to make a lot of noise on the console and in the logs.  

Maybe we could make this the official solution by adding support for it into ``Subtests`` and ``SubSubtests``?  e.g. for every ``option_name__WARNING__`` is found, do a ``self.logwarning(opt_value)`` on it?  This also comes with side-benefit possibility of automatically generating extra documentation for these options.