o365: ensure that IDs are not rendered with e-notation

[efd6]

Proposed commit message

o365: ensure that IDs are not rendered with e-notation

Due to JSON serialisation, numeric IDs may be rendered with e-notation
during flight. Ensure that this does not get fossilised into the
documents when they are converted to strings.

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.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Screenshots

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
83.6% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: af3aa4d

cc @efd6

[elasticmachine]

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

[chrisberkhout]

Good as is.

An alternative would be to have one script processor with a function that's run once for each field.

[elastic-vault-github-plugin-prod]

Package o365 - 2.18.5 containing this change is available at https://epr.elastic.co/package/o365/2.18.5/