[Deprecation service] Using i18n for deprecation messages

[Bamieh]

Adds a .mdx FAQ guide for deprecations service to help people get started.

Note:

We've decided to add i18n to the deprecation config objects. First we need to inject i18n into the deprecation function to enable teams to use it before adding it to the docs and guideline. This will be done in a follow up PR with code changes. Related: #99072

Previous PR: #99043

[alisonelizabeth]

Thanks @Bamieh for updating this FAQ! Left a couple nits, but overall LGTM.

[joshdover]

Should we add guidance on what we should do for deprecations like HTTP APIs? For instance, should those be logged in a specific format or with a specific meta field for filtering

[joshdover]

As a reader it's not clear to me the difference between plugin deprecations and Kibana deprecations and why this config is necessary to view the Kibana ones.

[Bamieh]

removed kibana deprecations in favor of plugin deprecations across the doc file. i've adedd an explanation why this config is needed:

The UA is in read-only mode and will be enabled up until the last minor before the next major release.

[Bamieh]

Should we add guidance on what we should do for deprecations like HTTP APIs? For instance, should those be logged in a specific format or with a specific meta field for filtering

@joshdover we dont have any concrete best practices around this yet. I believe we'd be developing them with time based on feedback and UA requirements. Currently we only use meta field for configs. if UA intends to expand on this field we'll document it here later on.

Do you have something specific in mind that we can add related to this?

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 4e602d6
• Storybooks Preview
• Documentation Changes

Metrics [docs]

✅ unchanged

History

• 💚 Build #134655 succeeded e5a25ba
• 💚 Build #134417 succeeded 6739b0b

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[joshdover]

we dont have any concrete best practices around this yet. I believe we'd be developing them with time based on feedback and UA requirements. Currently we only use meta field for configs. if UA intends to expand on this field we'll document it here later on.

Do you have something specific in mind that we can add related to this?

Let's discuss this as a follow up. I suspect we need to align on this pretty soon as we improve the upgrade experience.

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	7.x

This backport PR will be merged automatically after passing CI.