Remove VERSION string from library definitions

Problem/Motivation

The library definitions currently include a VERSION string in *.libraries.yml. In Drupal core, the VERSION constant refers to the Drupal core version. Contributed modules and themes should not rely on that value for asset versioning, because it can lead to stale assets being served after CSS/JS changes. See #2205027: VERSION in library declarations does not work for contributed/custom modules

This is especially risky behind CDNs and other intermediate caches: if the theme updates an asset file but the library version does not change, cache invalidation may not happen as expected, and users can receive outdated CSS/JS.

Steps to reproduce

• Install the module.
• See the inclusion of the css file that includes the file like /modules/contrib/navigation_extra/assets/css/navigation_extra_version.css?tayh9a
• Add a patch from for example #3573191: Environment color not working with newer version of Gin (5.0.11+) where the CSS is changed or change CSS yourself.
• See there is no change, even after a cache clear.

Proposed resolution

Remove the version definition in libraries.

Remaining tasks

Create and review MR.

User interface changes

None.

API changes

None.

Data model changes

None.