Remove VERSION from libraries.yml

Problem/Motivation

Using version: VERSION in a contrib or custom module's libraries.yml file can lead to significant caching issues, particularly when you need to update your module's assets frequently.

When you specify version: VERSION in your libraries.yml file, Drupal uses the core version number (like 9.4.1) as a query string parameter for your CSS and JavaScript files. This creates URLs like example.js?v=9.4.1 for your assets.

The problem with this approach is that these assets will be cached in browsers based on this version string, which only changes when Drupal core itself is updated. This means:

1. Your module's asset changes won't be reflected until a core update occurs
2. Users may continue to see outdated CSS or JavaScript even after you've deployed updates
3. Manual browser cache clearing becomes necessary for users to see changes

This is particularly problematic when using edge caching or CDN caching, as it becomes difficult to invalidate the cache when you make changes to your assets. Even running drush cr won't help in this situation because the version string remains tied to the core version.

Steps to reproduce

This can produce various problems after an update, as the old versions of assets might be loaded for users who have those cached. The only way to currently fix those to clear the browser cache.

Proposed resolution

Remove the version: VERSION lines from libraries.yml. By doing this, Drupal will use an automatically generated query string added to filenames. From the code documentation:

The string changes on every update or full cache flush, forcing browsers to load a new copy of the files as the URL changed.

See: web/core/lib/Drupal/Core/Asset/JsCollectionRenderer.php:62

The other option is to explicitly set the module's version on these lines and keep track of it when the version number changes/the asset is updated.