NEW Provide a consistent way of triggering flush

Provides an interface for classes to implement their own flush()
functionality. This function gets called early in a request on
all implementations of Flushable when flush=1|all is requested in the
URL
    
This fix came out of an issue where Requirements combined files were not
being cleaned up after dev/build?flush=1, due to the fact that flush
would only occur when you called it while on a page that used those
combined files, but not in any other contexts. This will now call flush
on any implementors of Flushable regardless of the context of where
flush was called.

In the case of `SSViewer::__construct()` doing a `Security::permissionFailure()`
if flush was requested but you don't have permission, I don't think that's needed
anymore. I tried putting the site in test mode and trying to flush, it still asks
to login even without the security check done there.

We also flush the cache in *any* case when `TestRunner::use_test_manifest()`
is called. I don't see any reason why you wouldn't want to flush the cache when
running tests.

@halkyon Comparing the performance of a full database heavy `DataObjectTest` run isn't really the point though, I want individual tests to run fast. For example, here's a single test that doesn't interact with the database: `phpunit --filter testUpdateStatic framework/tests/core/ConfigTest.php`. 1s before, 3.7s after. So 15s was an overstatement, but this is still 4x as slow for a single test. For a single database-based test like `phpunit --filter testBaseFieldsExcludedFromDb framework/tests/model/DataObjectTest.php`, the difference is also 1.5s to 4.3s.