Library should not be using the Drupal VERSION for the version

@codebymikey: We do want a version set (since we've had issues when there were no version set), could you add 1.26 rather than just removing the version, and then we will have an issue to increase the version counter on every new version of the module.

Closing this as a duplicate, looks like we fixed it in your other issue 🐛 Javascript cache bust variable remained constant Active