Use semantic versioning to manage GitLab VSCode Fork releases

MR: Pending

Description

Currently, the VSCode Fork uses timestamps to identify package releases, for example: 1.89.1-1.0.0-dev-20241119100914. This release identifier breaks tools used to maintain project dependencies such as the renovate-bot. We should replace these timestamps with the widely used semantic versioning convention explained in https://semver.org/

Acceptance Criteria

TODO: Fill out (required)

  • [Describe what must be achieved to complete this issue.]
  • [Describe another requirement needed to complete this issue.]
  • [Add additional acceptance criteria as needed.]

Technical Requirements

TODO: Fill out or delete (optional) [If applicable, please list out any technical requirements for this feature/enhancement.]

Design Requirements

TODO: Fill out or delete (optional) [If applicable, please provide a link to the design specifications for this feature/enhancement.]

Impact Assessment

TODO: Fill out or delete (optional) [Please describe the impact this feature/enhancement will have on the user experience and/or the product as a whole.]

User Story

TODO: Fill out or delete (optional) [Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality.]

Edited by Enrique Alcántara