TYPO3 Core

Idea is to transfer the table creation and layout within the db backend to have control about it on layout changes and to not depend on extensions to adapt layout if we need it in core.

It will propably become tricky in em to handle it fully automatically at this point (with whatever other db changes are lying around).

The best idea I've had until now is to do it in flush():
- We know final table names at this point
- Tables are truncated there anyway, we just always do an additional drop and create, it will be quick
- Caches are flushed on extension change anyway, together with the flow3 cache update patch the cache manager is able to flush() all defined caches, even if they are not instantiated.
- No overhead at runtime / in cache production
- Table names can be determined automatically by db backend, so tagsTable and dataTable settings are optional after the patch.

Until now I did not figured on how to do it best:
- Probably one or two sql resource blueprint files in t3lib/cache/backend/resource/ where we fiddle our current tables names into, or something like that
- The main table creation can probably be done by em sql compare magic (it should handle dbal for us for thinks like the Engin=Innodb line), but I have no idea for the actually needed code and didn't check this until now

I'm unsure if we should create an own issue for this and handle our issue here after we've changed the db backend.

@Björn: Do you have time and fun to hack on this issue?

Applied in changeset 0f6891581e13e91e195c09cde498c9e137609581.