Intercept metrics in test runner

[jaydeluca]

Now we're getting to the fun part...

This PR covers a few changes:

• Added the otel.nullaway-conventions plugin (as recommended here) and addressed all issues raised by it
• Added an interceptor in the test runner to collect metrics emitted during runs (when flag enabled) and writes them to .telemetry files within each instrumentation module directory
• Updated the instrumentation analyzer to look for these files and populate the module with the information
• Updated the YamlParser to write these metrics to the instrumentation-list.yaml file
• Adds a helper script that will target and run the tests only for the modules we have configured, and will clean up the temp files after completion

I wanted to keep this PR small-ish, so I didn't go through and start enabling this for other modules, but I will followup with that.

I am also going to play around with how we might handle situations where different metrics are emitted by different config options (like -Dotel.semconv-stability.opt-in=database, as an example), and how we might best display that information

Related to #13468

[jaydeluca]

@trask - from your question during the SIG meeting:

The {} bit is the placeholder for the exec command. Whatever files are found by find are inserted in place of the brackets. The + means to build up a long list of the found files and call the exec on all of them at once instead of one at a time, like the more traditional -exec {} ; variant.

https://serverfault.com/questions/72978/what-does-rm-do

[trask]

Suggested change

	**/.telemetry*
	.telemetry/

[jaydeluca]

there is a directory generated per instrumentation module

[trask]

it should work

if you only want to ignore it in the root, it would be different:

/.telemetry/