Add asset BundleManager & re-organize the asset helper classes

[jaxwilko]

This PR adds a new BundleManager class which is responsible for managing the different "asset bundles" available in Winter. Bundles will automatically be offered by the vite:create & mix:create scaffolding commands as option flags.

This allows us to:

• Have a single entity responsible for managing versions
• Allow the user to configure their own bundles / overwrite the existing bundles if desired
• Manage the update process better by reducing magic numbers in the system

I've also cleaned up some of the install logic and added some user feedback similar to create:plugin when running {$compiler}:create.

In addition to the above, this PR removes the majority of the fixtures for Mix/Vite configs and now lets subscribers modify the base config on the fly.

\System\Classes\Asset\BundleManager::instance()->registerCallback(function ($manager) {
    // Register a bundle (using a compiler as a key and having an array as a value means that the array 
    // will be squashed into the bundle when that compiler is being called, else the array will be discarded):
    $manager->registerBundle('jaxjs', [
        'jaxjs' => 'v1.0.0',
        'mix' => [
            'mix-jaxjs-adapter' => 'v1.2.0'
        ],
        'vite' => [
            'vite-jaxjs-adapter' => 'v1.6.0'
        ],
    ]);
    
    // Register a setup handler (is executed on install to allow for bundles to generate their own config
    // files / prep the plugin)
    $manager->registerSetupHandler('jaxjs', function (string $packagePath, string $packageType) {
        $this->writeFile(
            $packagePath . '/jax.js',
            File::get(__DIR__ . '/../fixtures/jax.js')
        );
    });

    // Register a scaffold handler (is executed during stub/config generation), `contentType`
    // can be: vite, mix, js, css.
    $manager->registerScaffoldHandler('jaxjs', function (string $contents, string $contentType) {
        return match ($contentType) {
            'mix' => $contents . PHP_EOL . <<<JAVASCRIPT
            console.log('jaxjs installed');
            JAVASCRIPT,
             'vite' => $contents . PHP_EOL . '// example',
            'css' => $content . PHP_EOL . $this->getFixture('css/jaxjs.css.fixture'),
            'js' => $this->getFixture('js/jaxjs.fixture')
            default => $contents
        };
    });
]);

Once the configs have been set, either via a config file, or from config calls in a plugin, the following can be ran in the CLI:

./artisan vite:create Acme.Plugin --jaxjs
# Or
./artisan mix:create Acme.Plugin --jaxjs

Plugins can call these methods to register handlers to modify either stub or config generation, or do additional tasks when the {$compiler}:create command is ran.

NOTE: setupHandlers & scaffoldHandlers are executed within the context of AssetCreate this means they have access to the internal properties of the class such as assetType (mix or vite) and have access to methods such as writeFile() & getFixture().

[bennothommo]

@jaxwilko you might consider putting the "groups" of packages in that same class and call it NodePackages. Then the commands could simply call the group in. You could even make it extensible - ie. allow plugins to define packages if the plugins themselves provide front-end functionality?

[jaxwilko]

@jaxwilko you might consider putting the "groups" of packages in that same class and call it NodePackages. Then the commands could simply call the group in. You could even make it extensible - ie. allow plugins to define packages if the plugins themselves provide front-end functionality?

Thy will be done

[jaxwilko]

Docs for new BundleManager features have been added here: wintercms/docs#203

completed