CMS Vue Plugins

Current situation:
Vue plugin deployment is currently a manual job of copying an XSLT and the bundle to the customer file cache, and then loading the plugin via the XSLT.
Loading via an XSLT works, but isn't really how we want to do this in the future.

Idea:
Most, if not all, plugins on the CMS will have a backend API to ensure the OData token (or other API token) isn't exposed to the customer.
We can have some standard endponts on all of these API's we create along the lines of FetchPluginXSLT and FetchPluginBundle.
The CMS gateway can then be updated to handle a Vue plugin type. The gateway will be aware of these standard endpoints and can use them to fetch and cache the bundle and XSLT, manage versions of the plugin and provide a central point for serving the plugin to customers instead of being on individual file caches.
Further, the APIs we are writing already have well defined and tested deployment processes which function well through the dev / qa / live lifecycle. So we wont need to create new deployment processes specifically for these plugins.