[APM] Add 'deactivate_...' agent configuration settings for EDOT Node.js

[trentm]

Summary

This makes the existing 'deactivate_all_instrumentations' and 'deactivate_instrumentations' agent configuration settings
available to EDOT Node.js agents (agent.name: opentelemetry/nodejs/elastic). (This follows on the recent #222883 that did the same for another config setting.)

This makes use of the newly added https://ela.st/edot-node-disable-instrs short URL that points to the current relevant anchor in the EDOT Node.js docs.

Screenshot of Agent Configuration section in Kibana showing to two newly available settings for an EDOT Node.js SDK configuration:

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
• Flaky Test Runner was used on any tests changed
• The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines

Identify risks

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.

• See some risk examples
• ...

[trentm]

@jackshirazi Are you okay with the re-wording here?

@intuibase @SergeyKleyman In the APM agents meeting yesterday, my understanding was that EDOT PHP was going to want deactivate_instrumentations and deactivate_all_instrumentations settings. Shall I add PHP to this PR as well?

If so, can you provide an appropriate link listing supported instrumentation names? For:

- [EDOT PHP](https://ela.st/???): for example "???"

[elasticmachine]

Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)

[cauemarcondes]

LGTM

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 224502 locally
cc: @trentm

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create automatically backports add a backport:* label or prevent reminders by adding the backport:skip label.
You can also create backports manually by running node scripts/backport --pr 224502 locally
cc: @trentm