Create settings necessary for an MVC Pipeline

[donker]

This PR creates the settings necessary for the MVC Pipeline. These are the following:

1. A site setting which determines the entire site's pipeline behavior: WebForms (default), MVC or Auto.The value becomes part of the PortalSettings. In the UI this can be found on the PB under Site Settings > Site Behavior > More at the bottom of the panel.
2. A page setting which tells DNN how to render: Inherited (default), WebForms, MVC. The setting is stored in the TabSettings. It is visible in the UI on the PB under Pages > Advanced > More towards the bottom.
3. A new field "MvcControlClass" on the ModuleControls table which informs DNN whether the module control supports the new pipeline. The value will be a class reference or empty in case there is no explicit support for MVC. There is support for this field in the PB extensions module (on the module control editor) and in the module's manifest (.dnn file)

This is the first PR in a series of PRs that aim to build out the MVC Pipeline functionality in DNN. It targets a feature branch as all PRs will need to be in before this can be merged into the main branch of the project. The reason for a more granular approach to the PRs is to make them easier to verify for the reviewers.

[bdukes]

@donker is the current status of this PR that you're looking into unit test failures?

[thienvc]

Excuse me, but I'd like to ask if the MVC Pipeline concept is still being developed?

[sachatrauwaen]

Excuse me, but I'd like to ask if the MVC Pipeline concept is still being developed?

Yes it is under review

[mitchelsellers]

Excuse me, but I'd like to ask if the MVC Pipeline concept is still being developed?

As Sacha mentioned yes, the current focus is on trying to get this into a state that we can review it for inclusion without introducing breaking changes to the larger DNN Platform install base. As you can see some of the feedback on this particular PR addresses, for example the proper location to introduce new features, or settings to do so in a manner that will not break prior installations, and also not add too much to the API Surface for long-term support.