Marc Pichler

@iancward thank you for your contribution - due to organization policy, we unfortunately we cannot accept any PRs without the CLA signed (see [here](https://github.com/open-telemetry/opentelemetry-js-contrib/pull/2509#issuecomment-2442541825) for instructions on how to do...

I'm also happy to dedicate some time to this as we're using this package over at the [open-telemetry/opentelemetry-js](https://github.com/open-telemetry/opentelemetry-js/) repository. :slightly_smiling_face:

just ran this locally - the gcp-metadata spans are now gone 🙂

FYI @abhee11(component owner)

cc @blumamir - I would appreciate you having another look if you find some time 🙂

@seemk conflicts need to be resovled one last time then this is good to merge 🙂

@timfish It's yours, thanks for looking into it :slightly_smiling_face:

cc @JamieDanielson @pkanal (component owners)

@seemk - please update the PR with owners according to the [contributing guidelines ](https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/CONTRIBUTING.md#new-instrumentation) (similar situation as with #2187) if you're still planning to get this instrumentation added. Thanks! 🙂

>> Could we mark `@open-telemetry/lambda-extension-approvers` or somesuch as the owner of the lambda instrumentation? Essentially this component is used as part of the otel-lambda repo/build. @johnbley absolutely, we'd very much...