Make sure statistics for recording are saved if recording is interupted due to stopping the component

- is not connected yet

- query and store needs to call directlyStore, otherwise contents are only put into the buffer but not saved
- tested in Simulation

- time since last acceptance is now calculated per entity and thus filters the snapshots per snapshot for this one entity

- added lastStarted and lastStopped fields in addition to firstStarted and firstStopped
- filter statistics are reset when start recording is pressed
	- resets #accepted, #rejected, additional_time

- changed default path for LTM export to /tmp/ltm/MemoryExport
- changed trigger for when statistics are saved
	- saving directly after a recording was stopped
	- only save statistics if a valid time of start for the recording was detected
	- do not save empty statistics files
	- if no snapshots were accepted or rejected no filter statistics are added and if that is the case for all filters an exception is thrown (and catched which then leads to an empty statistic)
- changed namespace of MemoryBase.cpp to match MemoryBase.h
- FrequencyFilter fix looks at each entity seperately when comparing lastStored times (should solve issues with multiple provider/core segments in one memory)
	- needs to be tested

(tested in simulation)

Usage:
add ' "ExrConverter": {} ' to ltm.configuration property of VisionMemory

- MemoryBase: added PNGConverter as standard for processors to use

- MemoryToIceAdapter: put stopping of recording into its own thread and detached it to solve the problem of the GUI freezing if there is still data left to store after pressing stop
- Memory: Added information to print into log when storing of all data for this memory is finished
- BufferedMemoryMixin: removed unnecessary threading/parallelization and code that did not work (bufferFinished())

provider segment and core segment information is only added to the working memory object that will be exported when the corresponding episode snapshots that are exported have this core- or provider-segment
The log prints an info statement when core- and provider segments are exported that do not have aron type information.

Problem: when storing ltm a new wm is created and the entity snapshots are added, but the aron-type information of the server::wm is lost

Fix: new method that adds core and provider segments to newly created armem::wm to which entity snapshots are added
This needs a better solution, but export of aron-type information does work like this

# Conflicts:
#	source/RobotAPI/libraries/armem/core/MemoryID.cpp

Changes for ARMAR-7

See merge request !417

Resolve "Fix usage of custom skill blueprints"

Closes #140

See merge request !416

This commit introduces the SkillWithContextBlueprint, this allows for the creation of Skills that require a context to be connected. Also, changes were made to the SkillProviderComponentPlugin where naming of some skill factories was corrected.

Use common Names type for object classes, add getObjectClasses to client

See merge request !415

add FramedPositionAndOrientation aron type and add constructor in pose and framed pose related to this type

Skills: Fix missing result for the last status update if a skill succeeds

See merge request !412

- no comparison
- better human readability of json
- added runtime of recording  and lifetime of filter

also removed some old ARMARX_INFO prints

- returns empty statistics if getting Statistics from processors does not work (e.g. no processors were used)
- calls save_statistics method from Plugin.cpp after disconnecting component
- save_statistics now takes exportPath and exportName as parameters to build the correct path to the statistics directory
	- statistics directory can be found at: exportPath/Date/exportName/MemoryName/Statistics

- removed functionality that was only needed when recording multiple LTMs in parallel
- removed some old comments and some old ARMARX_INFO code
- added some new try-catch blocks and appropriate warnings

EntityInstance: changed bool to actually not save data in aron.json when extracting
Memory.cpp: rebased code to add date to memory base path to DiskStorageMixin
DiskStorageMixin: added code to save exports of LTM at exportPath/Date/exportName/MemoryName...

# Conflicts:
#	source/RobotAPI/libraries/armem/server/ltm/EntityInstance.cpp

ExportName for LTM exports can be set by adjusting property config file and ArmarX.MemoryName.mem.ltm.exportName property

Also stopped cloning aron data before extraction because that was only necessary for multiple LTMs

Add introspection about timings in Robot state memory

See merge request !414