[o365_metrics,checkpoint_harmony_endpoint] Fix upto/Extention typos in user-facing text

[MukundaKatta]

Refs #18497.

Picks up the two typo families the Text Auditor workflow flagged. Both are user-visible strings (Kibana help text and field descriptions), no behaviour change required.

Changes

upto → up to (o365_metrics, 4 occurrences)

...can take upto 48h or more to be available... → ...can take up to 48h or more to be available...

• packages/o365_metrics/data_stream/groups_activity_group_detail/manifest.yml
• packages/o365_metrics/data_stream/viva_engage_groups_activity_group_detail/manifest.yml
• packages/o365_metrics/data_stream/onedrive_usage_account_detail/manifest.yml
• packages/o365_metrics/data_stream/teams_user_activity_user_detail/manifest.yml

Extention → Extension (checkpoint_harmony_endpoint, 2 occurrences)

Browser Extention version → Browser Extension version

• packages/checkpoint_harmony_endpoint/data_stream/zerophishing/fields/fields.yml
• packages/checkpoint_harmony_endpoint/docs/README.md

Version bumps

Per the repo's release policy, each touched package gets a patch bump with a changelog entry:

• o365_metrics: 1.1.1 → 1.1.2 (bugfix)
• checkpoint_harmony_endpoint: 1.2.0 → 1.2.1 (bugfix)

The link: fields in the new changelog entries currently point at PR NNN — I'll swap them to this PR's number once GitHub assigns it (or a reviewer is welcome to push that tweak before merging).

[cla-checker-service]

❌ Author of the following commits did not sign a Contributor Agreement:
b285d4f, 33bec42

Please, read and sign the above mentioned agreement if you want to contribute to this project

[elastic-vault-github-plugin-prod]

Reviewers

Buildkite won't run for external contributors automatically; you need to add a comment:

• /test : will kick off a build in Buildkite.

NOTE: https://github.com/elastic/integrations/blob/main/.buildkite/pull-requests.json contains all those details.

[elasticmachine]

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

[kcreddy]

@MukundaKatta, thanks for the contribution. Can you please sign the CLA so we can review this PR?
Also the merge conflicts must be resolved for the CI job to run.

[botelastic]

Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

[botelastic]

Hi! This PR has been stale for a while and we're going to close it as part of our cleanup procedure. We appreciate your contribution and would like to apologize if we have not been able to review it, due to the current heavy load of the team. Feel free to re-open this PR if you think it should stay open and is worth rebasing. Thank you for your contribution!