[datadog_service_account_application_key] Fix scoped key example

[lot-koichi]

What

This updates the datadog_service_account_application_key scoped key example.

• Remove the example that passes permission IDs returned by data.datadog_permissions into scopes
• Use Datadog authorization scope names directly, which is what the API accepts
• Regenerate docs/resources/service_account_application_key.md from the updated example

Why

As described in #3819, the current example suggests passing permission IDs into application key scopes. Datadog rejects that request with Invalid scopes.

The provider implementation and acceptance tests already use scope names directly, so this change aligns the documentation example with the provider behavior and Datadog API expectations.

References

• Fixes Docs: service_account_application_key scopes example uses permission IDs #3819
• Requested labels: changelog/documentation, resource/datadog_service_account_application_key

Tests

• PASS: make fmtcheck
• PASS: make docs
• PASS: make check-docs
• PASS: make test TEST="./datadog ./datadog/dashboardmapping ./datadog/fwprovider ./datadog/fwprovider/observability_pipeline ./datadog/internal/customtypes ./datadog/internal/fwutils ./datadog/internal/planmodifiers ./datadog/internal/utils ./datadog/internal/validators ./version"
• NOTE: full make test was attempted, but datadog/tests includes acceptance tests and failed because DD_TEST_CLIENT_API_KEY is not set in this local environment.

[urseberry]

DOCS-14577 created for review

[OliviaShoup]

hey, thanks so much for the PR! we always appreciate when people help us update the documentation :)

[fpighi]

@lot-koichi we require commits to be signed. Can you please make sure of that? Once done the PR will be merged. Thank you again.

[lot-koichi]

@lot-koichi we require commits to be signed. Can you please make sure of that? Once done the PR will be merged. Thank you again.

@fpighi Thank you for comment. I signed the commit, please take a look!