Define the semantic versioning strategy

**Is your feature request related to a problem? Please describe.**
There is a general desire to support a semantic versioning model across specification artifacts, but we don't have effective tooling to do so. OSGi manifests are inconsistently being used to provide some aspect of this under one module system. We need a general approach with guidelines on usage.

**Describe the solution you'd like**
We need Jakarta supported tooling in place along with usage guidelines.

**Describe alternatives you've considered**
There are OSGi annotations and plugins that support the feature. However, there was not universal acceptance of whether such external tools should be employed in Jakarta.

**Additional context**
A discussion on this topic occurred in a platform meeting, and the following dev thread was started to open the conversation:
https://www.eclipse.org/lists/jakartaee-platform-dev/msg02761.html

Start with the linked platform-dev discussion and the platform meeting context, since no repository files or tests are named. The work is complete when Jakarta has an agreed semantic-versioning approach for specification artifacts, supported tooling, and documented usage guidelines.

Written by the indexing model from the issue text.