Add Vite support

[czernika]

This PR adds Vite support if user wants to use it since Vite is already bundled with Acorn package.

I found that it almost working but this line causing the problem as it expects to return a string but instead uses \Roots\asset() function which returns Asset object therefore fails. I believe I cannot change Illuminate content so I just extend a new Vite class with Laravel's one and change one method

Usage example with laravel-vite-plugin with basic setup

// vite.config

import { defineConfig } from 'vite';
import laravel from 'laravel-vite-plugin';

export default defineConfig({
    plugins: [
        laravel('resources/js/app.js'),
    ],
});

Needs to define vite as default manifest

// config/assets.php

return [
    'default' => 'vite',

    'manifests' => [
        'theme' => [
           // ...
        ],
        'vite' => [
            'path' => get_theme_file_path('public'),
            'url' => get_theme_file_uri('public'),
            'bundles' => get_theme_file_path('public/build/manifest.json'),
        ],
    ]
];

and inject assets in the head (it is not using wp_enqueue_ functions) something like

// app/setup.php

add_action('wp_head', function () {
  echo app('assets.vite')('resources/js/app.js');
});

For a custom vite configuration (let's say I need to use another manifest filename) we still can use Laravel API for Vite

// vite.config.js

export default defineConfig({
    build: {
      manifest: 'custom-manifest.json'
    },
    plugins: [
        laravel('resources/js/app.js'),
    ],
});

// setup.php
add_action('wp_head', function () {
  echo app('assets.vite')->useManifestFilename('custom-manifest.json')('resources/js/app.js');
});

// config/assets.php
// Change manifest name
'bundles' => get_theme_file_path('public/build/custom-manifest.json'),