Version upgrades and cleanups

This PR aims to bring the BlogBundle more in line with the [CMF Bundle Standards](http://symfony.com/doc/current/cmf/contributing/bundles.html).

##### General Changes
* Updated dependencies to ``CMF 1.2.*``
* Updated routing configuration to work with ``RoutingAutoBundle 1.0.*``
* Parameter and service ID names have been changed to match the conventions laid out in the standards
* DI in general got cleaned up with the intent of making it easier for 3rd party bundles to extend the BlogBundle

##### Persistence
* ``Blog`` and ``Post`` have been refactored into the Model and Doctrine/Phpcr namespaces.
* Their PHPCR mapping files were likewise relocated into Resources/config/doctrine-phpcr
* The mapping files are now auto-loaded by a ``DoctrinePhpcrMappingsPass``, if the class is found
* Added a ``GenericInitializer`` service to create the ``cmf_blog.blog_basepath`` if it's not found
* Rewrote the ``PostRepository`` to support searching by an array input-verified with the OptionsResolver

##### Front End
* Separated ``BlogController`` into ``BlogController`` and ``PostController``
* Templates were moved, renamed and refactored accordingly. Added markup for easier styling (still on BS2)

##### New Features
* Added (optional) route to list blogs
* Added (optional) pagination support, using the ``KnpPaginatorBundle``
* Added (optional) PHPCR data fixture to ease development

##### Known Issues
* Make sure configuration is loadable when defined as XML
* The XML schema file for the config is out-of-date with Configuration
* Translatable content. It might work; untested.

Addresses issues #53 and #57 
there is autoname but that can only generate random names (theoretically with prefix but phpcr-odm does not support that yet).

we should really do this, it can't be that hard. we could even have expression language. i would do it the other way round, on the nodename. then it would just be a new type of id generator...