Update version tag in libraries.yml file

An often forgotten nit pik is the version: tag in libraries files which will be placed on the end of the library path to tell browser cache if it is the same or not.

Problem/Motivation

The "version:" tags in libraries.yml files keep libraries' files cached in browsers per module version, which makes only sense if updated with the module version. Otherwise: This can cause fixed bugs to be unresolved when updating this module separate from a Drupal core update. Sadly there is no version: VERSION for reference to module version, only for core which makes no sense here at all. For regarding core issue please follow: #2205027: VERSION in library declarations does not work for contributed/custom modules

Proposed resolution

Remove all "version: 8xx" lines from the libraries.yml files or update them with the module version. Caching these static files should not be needed in all cases whatsoever, but if for some reason this is wanted behavior, then the version should at least be set to something relevant to the library definition instead of a Drupal core version or even worse (like at the moment) to an older module version.

Committed solution: updated version tag to 4.x