Implement "context" support
It should be possible to put FLOW3 into different environment contexts. Examples are "optimized", "production", "development" and "testing".
Other parts may then behave accordingly, for example the AOP would adjust the caching of the proxy classes depending on the selected mode.
See also #339 about Components.ini format.
- FLOW3: (Reflection) Added getProperty() to T3_FLOW3_Reflection_Class. Fixes #370.
- FLOW3: (Cache) Implemented load() support for the File backend. Addresses #368.
- FLOW3: (Component) The component manager's default context is now "Development". Relates to #23.
- Testing: The Base Testcase now sets the cloned component manager's context to "Testing".