fix, feat: use static string for Vue LSP version & add a GitHub Action to auto detect new version

[cuongvuong-phoenix]

As mentioned in #23, I think it's best to have a static version embedded into each version of the extension to:

• Prevent possible breaking changes in the future.
• Allow users to choose a specific version of Zed's Vue extension corresponding to a Vue LSP version.
• Avoid abusing NPM/GitHub APIs because every time a user opens Zed, the extension will send a request to get the latest version and check against the local version.
  I recently encountered an issue with the "Snippets" extension and got errors due to GitHub API rate limit...

In this PR, I also added a GitHub Action to help update to the latest version of Vue LSP every 12 hours and automatically create a PR that bumps both the static version string and Cargo.toml. The workflow runs quite fast (10-15s), you can check the result in my forked repo.

[ThatOneCalculator]

LGTM