fix: Do not reuse requestOptions object

[tommoor]

What does this PR do?

Ensures a fresh options object is passed to request on each request.

Motivation

This is good practice and protects against potential memory leaks such as getsentry/sentry-javascript#8654 which just cost me several days of debugging time.

Plugin Checklist

• Unit tests.
• TypeScript definitions.
• TypeScript tests.
• API documentation.
• CircleCI jobs/workflows.
• Plugin is exported.

Additional Notes

Security

Datadog employees:

• If this PR touches code that signs or publishes builds or packages, or handles credentials of any kind, I've requested a review from @DataDog/security-design-and-guidance.
• This PR doesn't touch any of that.

Unsure? Have a question? Request a review!

[simon-id]

Hi @tommoor, thank you for the contribution and sorry for the delayed answer due to the holiday season!

I've reviewed your PR and argument, and I agree I made a small oversight by not taking into account the potential third party libraries that would piggyback on the requestOptions object and mutate it.
I've cherrypicked your commit in this PR #3959 (for CI security reasons), and I'll complete it by updating the relevant tests.

Next time you're running into an issue that only happens when dd-trace is enabled, I suggest you go directly through our customer support, for a faster response, and easier visibility.

[simon-id]

Merged in #3959