Build semver checking into instrumentation registration

[kmudduluru]

Description

Is your feature request related to a problem? Please describe.
There have been a few times we have to add semver checks before registering something or have forked logic to determine what to do for a given module. We could cut down on fragmented version checks by building it into both the customer facing API and our internal shim.

Feature Description
allow a semver range to be specified when registering instrumentation in both API and shim.

Additional context
If you search for semver. in agent and external modules we have several use cases. I know this required us to bring semver into the package but also caused some toil with a botched release: https://github.com/newrelic/node-newrelic-aws-sdk/blob/main/index.js

Look into this issue for more details on this ticket - https://new-relic.atlassian.net/browse/NR-133374

[workato-integration]

https://new-relic.atlassian.net/browse/NR-304767