incorrect resource lifetimes due to static data

[Thanduriel]

Currently significant parts of the model are constructed and managed through ConfiguredModule::configuredModules and therefore have static lifetimes. This makes resource management via RAII challenging since the order of init/release is hard to track and destructors will only be called during the epilogue of main.

A concrete example for a problem this causes can be found in the GPU code. Usage of the GPU requires both manual initialize and finalize calls and the management of memory buffers. Currently the simulation will always terminate with an exception because the buffers are freed by a destructor which is only called after the finalize.

The easiest solution would probably be to make the ConfiguredModule data non-static and to introduce a finalize call.

[timspainNERSC]

A greater problem is the static data at the foundation of every Module<>.

Also check the rest of the infrastructure in core/src/include/*.hpp for static data members.

[timspainNERSC]

Classes to look at:

• [x] ConfigMap
• [x] Configurator
• [x] Configured<>
• [x] ConfiguredModule
• [x] FileCallbackCloser
• [x] Iterator
• [x] MissingData
• [x] ModelComponent
• [x] ModelConfig
• [x] Module<>
• [x] ParaGridIO
• [x] ScopedTimer
• [x] Timer