Update how instrumentation is tracked for subscribers #3575
Description
Description
In #3408 we added subscriber packages into require in the middle and import in the middle purely for incrementing the supportability on require metric. Previous to that #3309 added the code into the handler, but this was only incremented if you used an instrumented method. Both aren't ideal and the former is now defeating the purpose of migrating to subscriber based instrumentation which is that import in the middle cannot properly wrap ESM packages at times.
Acceptance Criteria
Develop a new mechanism for tracking subscriber based tracking metrics of:
Supportability/Features/Instrumentation/OnRequire/<pkg>
Supportability/Features/Instrumentation/OnRequire/<pkg>/Version/<semver-major-version>
Design Consideration/Limitations
Since these are only used by internal folks to track adoption, usage, we could create a new set of metrics but they still need to have both a metric for package name and package name by version.