[8.16](backport #4517) [apm] Update Applications nav subsection from "Services" to "Service inventory"

[mergify[bot]]

Description

Update the Applications nav subsection from Services to Service Inventory. Note: The page title appears to still be Services so I only updated references to the nav.

Documentation sets edited in this PR

Check all that apply.

• [x] Stateful (docs/en/observability/*)
• [x] Serverless (docs/en/serverless/*)
• [ ] Integrations Developer Guide (docs/en/integrations/*)
• [ ] None of the above

Related issue

Closes #4447

Checklist

• [ ] Product/Engineering Review
• [ ] Writer Review

Follow-up tasks

Select one.

• This PR does not need to be ported to another doc set because:
  • [ ] The concepts in this PR only apply to one doc set (serverless or stateful)
  • [x] The PR contains edits to both doc sets (serverless and stateful)
• This PR needs to be ported to another doc set:
  • [ ] Port to stateful docs: \
  • [ ] Port to serverless docs: \

    ---

    This is an automatic backport of pull request #4517 done by Mergify.

[mergify[bot]]

Cherry-pick of a24b240a171d919c1de3461acebdbd5feb57c866 has failed:

On branch mergify/bp/8.16/pr-4517
Your branch is up to date with 'origin/8.16'.

You are currently cherry-picking commit a24b240a.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
    modified:   docs/en/observability/apm/view-and-analyze/ui-overview/services.asciidoc
    modified:   docs/en/observability/monitor-k8s/monitor-k8s-application-performance.asciidoc

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
    deleted by us:   docs/en/serverless/apm/apm-find-transaction-latency-and-failure-correlations.asciidoc
    deleted by us:   docs/en/serverless/apm/apm-get-started.asciidoc
    deleted by us:   docs/en/serverless/apm/apm-ui-services.asciidoc

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[github-actions[bot]]

A documentation preview will be available soon.

• 🔨 Buildkite builds
• 📚 HTML diff
• 📙 Preview page

Request a new doc build by commenting

* Rebuild this PR: `run docs-build` * Rebuild this PR and all Elastic docs: `run docs-build rebuild` _{`run docs-build` is much faster than `run docs-build rebuild`. A `rebuild` should only be needed in rare situations. If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status [here](https://buildkite.com/elastic/docs-build).}