This PR will move DNN away from the ClientDependencyCore project and replace this with our own (simplified) logic for managing client dependencies.

Motivation

We do this for two main reasons:

1. The CDF has gone stale and all immediate potential replacements have also gone stale
2. The CDF will not allow us to include an MVC pipeline and hinders further development of DNN

Overview of Changes

The main changes are in the System.Web.Client library that managed most interaction with the CDF. The central class ClientDependencyManager now reroutes calls to the new logic and has been marked as deprecated. The new logic is concentrated in System.Web.Client.ResourceManagement and consists of an injectable IClientResourceController. This controller is used as follows to add a resource:

    this.clientResourcesController
        .CreateScript()
        .FromSrc("~/Resources/Search/Search.js")
        .SetPriority(FileOrder.Js.DefaultPriority)
        .SetProvider(ClientResourceProviders.DnnFormBottomProvider)
        .Register();

It is important to call Register() at the end to add the resource. Various extension methods allow you to specify specific attributes to be added for the resource such as async and defer. There are also shorthand extensions in the DotNetNukelIbrary project to register a script with defaults: this.clientResourcesController.RegisterScript("~/Resources/Search/Search.js");

Breaking Changes

Note that this PR removes the ability to minify and bundle from the framework. Our motivation to cut support for this is:

1. It is a non-trivial task to reimplement these and carries a significant risk
2. Modern front-end development uses minifying as a build step when rolling out to production, begging the question why the framework should do this
3. HTTP2 has reduced the need for bundling as a way to speed page load. Instead, server side bundling would now just add needless processing and management.

This PR addresses #6643