aws_bedrock,google_scc,microsoft_defender_cloud,ti_threatconnect: fix renameKeys

[efd6]

Proposed commit message

See title.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Screenshots

[elasticmachine]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 1446be5

History

• 💔 Build #11631 failed 2540d5fde636f06a88fa2c6f95b8523b0132a26e
• 💔 Build #11630 failed 0ada10a55d3bc6a295553732ff25b5f0fd4c67de

cc @efd6

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[elasticmachine]

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

[elasticmachine]

Package aws_bedrock - 0.1.3 containing this change is available at https://epr.elastic.co/search?package=aws_bedrock

[elasticmachine]

Package google_scc - 1.2.1 containing this change is available at https://epr.elastic.co/search?package=google_scc

[elasticmachine]

Package microsoft_defender_cloud - 1.1.2 containing this change is available at https://epr.elastic.co/search?package=microsoft_defender_cloud

[elasticmachine]

Package ti_threatconnect - 0.6.1 containing this change is available at https://epr.elastic.co/search?package=ti_threatconnect