Using latest javaagent is risky

[breedx-splk]

Not entirely sure what we might want to do about this, but I just wanted to point out that using the "latest" tagged javaagent is a bit risky, especially if otelify.sh makes it into production. A user would be quite surprised if a simple restart causes a major (semver) update.

A couple of possibilities:

1. With documentation, make it very clear that this tool should not be used in production environments.
2. Pin to the latest major version

Of course with 2) there is a bit more work to figure out what the latest version in a major line is, and there is manual maintenance to be done after a major version upgrade.

[svrnm]

Thanks for calling this out, pinning the version would be a great feature, my initial idea was something like I described in #7, but maybe more is needed:

• As you suggested, adding wording to the documentation that this is primarily intended for non-production environments
• Print a message to the console by default that shows the currently used version + a message suggesting to pin it (if Add the ability to pin versions of zero code instrumentations #7 gets implemented)