RazorViewEngineOptions shouldn't be a property of MvcOptions

[pranavkm]

This was based off a conversation with @loudej when we were discussing MvcRazorHost. The idea is RazorViewEngine is the default implementation we configure, but shouldn't be tied to MvcOptions. Instead it would be a separate top level options type that can be configured independently.

.Setup<MvcOptions>(options => { })
.Setup<RazorOptions>(options => {});

[yishaigalatzer]

@pranavkm @loudej can someone explain why we want it this way? Putting things in MVC options makes it easier to find them, and since the view engine is tightly coupled to MVC, it's not really clear to me why the separation.

is it to make Web Pages feel disconnected from MVC when we implement it or is there another idea behind this?

[pranavkm]

ViewLocationExpanders currently located on MvcOptions also needs to be part of this.

[pranavkm]

Fixed as part of ad8ab4b