Feature/introduce version package

[pchila]

What does this PR do?

Introduce semver-compliant version package to be used for upgrade to specific snapshot build.

Why is it important?

We need a way to parse correctly versions like x.y.z-SNAPSHOT+buildID, since the code is small enough I chose to introduce our own version package so that we can tailor it to our release name conventions if we need to (snapshot, emergency releases etc.)
We also removed a direct dependency on an external library by adding ~160 lines of code which is not too bad since it comes with the advantage of full control over the version parsing for elastic agent

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• [ ] I have made corresponding changes to the documentation
• [ ] I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• [ ] I have added an entry in ./changelog/fragments using the changelog tool
• [ ] I have added an integration test or an E2E test

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• Relates Feature/allow upgrade to snapshots #2704

Use cases

Screenshots

Logs

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

[mergify]

This pull request does not have a backport label. Could you fix it @pchila? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-05-31T17:13:35.211+0000

• Duration: 21 min 9 sec

Test stats 🧪

Test	Results
Failed	0
Passed	5795
Skipped	19
Total	5814

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages.

• run integration tests : Run the Elastic Agent Integration tests.

• run end-to-end tests : Generate the packages and run the E2E Tests.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	98.63% (72/73)	👍 0.019
Files	68.4% (171/250)	👍 0.127
Classes	67.019% (317/473)	👎 -0.002
Methods	53.838% (968/1798)	👍 0.16
Lines	39.603% (11092/28008)	👍 0.121
Conditionals	100.0% (0/0)	💚

[ycombinator]

Could you include the removal of the github.com/Masterminds/semver module and any associated changes in this PR? That way, before and after this PR, we only have one way to parse and work with versions in the EA codebase. Thanks!

[ycombinator]

This new package is being used in integration/E2E tests and we're backporting those to 8.8. So backporting this PR here here to 8.8 as well.