feat: use build version aware caching

[ttytm]

The changes add a version-aware cache. This fixes the issue where an old cache would prevent updates and bug fixes from becoming visible to users.

obsolete

The versioning follows the same scheme as we do for the metadata/stubs. But instead of using a hardcoded version for the metadata(which is handled separately and changes less often) the changes in the PR add a more dynamic handling for the analyzer's indexing cache based on the build commit. This should be appropriate as it is affected by most commits to the project.

Refs to stubs versioning:

• setup:

  v-analyzer/server/general.v

  Line 345 in 44c804d

  fn (mut ls LanguageServer) setup_stubs() {

• version file:

  v-analyzer/config/constants.v

  Line 39 in 44c804d

  pub const analyzer_stubs_version_path = os.join_path(analyzer_stubs_path, 'version.txt')

• manual versioning:

  v-analyzer/server/language_server.v

  Lines 47 to 50 in 44c804d

  	// stubs_version incremented on each change in stubs
  	//
  	// See also `LanguageServer.setup_stubs()`
  	stubs_version int = 1