User-Based Deploys for Classic WebJars

[jamesward]

Since this WebJar needs frequent updates I started working on a way to support those via https://webjars.org

It works by defining a metadata file that gives the WebJar an artifact ID and sets properties to define:

• name
• repo
• requirejs.main
• base.dir

Example:
https://github.com/webjars/webjars-classic/blob/main/swagger-ui.properties

I've deployed the swagger-ui WebJar via https://webjars.org using this setup. The resulting POM is:
https://repo1.maven.org/maven2/org/webjars/swagger-ui/5.14.0/swagger-ui-5.14.0.pom

The properties could enable more flexibility than currently exists, but likely won't be able to cover all of the current setups for all WebJars, in which case we can use the old mechanism.

All metadata definitions will live in:
https://github.com/webjars/webjars-classic

This enables us to control the artifact IDs and enable switching existing Classic WebJars to this approach without changing the coordinates.

My plan is to validate this approach works, and then migrate the most frequently updated Classic WebJars to this setup.