Implement Semantic-Version Tool for vets-api

[JoeTice]

Description

Assess the feasibility and benefits of adopting the semantic-version tool for managing versioning in vets-api, potentially replacing codacy/[email protected].

---

Tasks

• Evaluate the capabilities and integration process of semantic-version.
• Compare semantic-version with the current versioning tool in terms of functionality and efficiency.
• Consult with Patrick on the potential switch and, if agreed upon, prepare a PR for vets-api.

Acceptance Criteria

• A comprehensive evaluation of semantic-version is conducted.
• A decision is made regarding the replacement of the current versioning tool.
• If replacing, a PR is successfully merged into vets-api implementing semantic-version.

[rmtolmach]

Because of the work done in these three PRs:

• Send version information to datadog vets-api#16418
• https://github.com/department-of-veterans-affairs/vsp-infra-application-manifests/pull/2807
• Add datadog version tag configuration vets-api#16383

logs in Datadog can be traced back to the deployment. Once we have semantic versioning working, DD_VERSION can be populated with the version instead of the sha, like it is now. Slack thread for context.

[ericboehs]

Let's rework to be "Implement". Ben suggested a solution we're already using on Platform.