Starting to get a UI around content type management

- added a DisplayName to the ContentTypeDefinition
- added a CreateRouteValues rvd to go along with the existing display and edit
- set default display, edit and create route values for ContentItemMetadata (* should get fallback route values in a different manner. probably not good to refer to an area, even by string, in core from the fwk)
- starting to shape up the content type list into a more consistent UI
- added create type action, view, etc. for creating new content types
 - supporting service has a few default parts hard-coded for now

--HG--
branch : dev

src/Orchard.Core.Tests/Feeds/Controllers/FeedControllerTests.cs

@@ -167,7 +167,7 @@ namespace Orchard.Core.Tests.Feeds.Controllers {
 
             var mockContentManager = new Mock<IContentManager>();
             mockContentManager.Setup(x => x.GetItemMetadata(It.IsAny<IContent>()))
-                .Returns(new ContentItemMetadata { DisplayText = "foo" });
+                .Returns(new ContentItemMetadata(hello) { DisplayText = "foo" });
 
             var builder = new ContainerBuilder();
             //builder.RegisterModule(new ImplicitCollectionSupportModule());