[Logs/Metrics UI] Add deprecated field configuration to Deprecations API

[Zacqary]

Summary

Closes #113166

This PR adds two different types of deprecations for the Source Configuration fields:

1. A critical deprecation for any fields that are set to a non-default, non-ECS-compliant value, in any source configuration
2. A warning deprecation for any presence in kibana.yml of xpack.infra.sources.default.fields.{DEPRECATED FIELD KEY}. This is only a warning because these values only affect anything the very first time the user runs Kibana, and don't seem to be able to update the source configuration later on.

To test

Configure deprecated fields

1. In kibana.dev.yml, set xpack.infra.sources.default.fields.{DEPRECATED FIELD KEY} to a different value. For example, set xpack.infra.sources.default.fields.timestamp to not-@timestamp
2. Open the source configuration in the settings page, and ensure the field is changed and editable

Check the Upgrade Assistant

1. Edit lines https://github.com/elastic/kibana/blob/master/x-pack/plugins/upgrade_assistant/public/plugin.ts#L25-L29 to say

const kibanaVersionInfo = {
  currentMajor: kibanaVersion.major - 1,
  prevMajor: kibanaVersion.major - 2,
  nextMajor: kibanaVersion.major,
};

2. Delete lines https://github.com/elastic/kibana/blob/master/x-pack/plugins/upgrade_assistant/public/application/app.tsx#L35-L37
3. Navigate to app/management/stack/upgrade_assistant and ensure you see warnings about the deprecated fields.

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Unit or functional tests were updated or added to match the most common scenarios

[simianhacker]

I think we should remove the actual field names from the translations since those need to remain untranslated. I was going to suggest things like tiebreaker, pod ID, container ID, host name, etc but I can't decide if it's OK to translate those OR not. But the actual literal field names need to remain untranslated.

[kibanamachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request
• Commit: 42ebefb
• Storybooks Preview
• Pipeline Steps (look for red circles / failed steps)
• Interpreting CI Failures
• Documentation Changes

Failed CI Steps

• Jest Unit Tests
• Quick Commit Checks
• Lint: eslint

---

Test Failures

Kibana Pipeline / jest / Jest Tests.src/plugins/dashboard/public/application/hooks.Dashboard container lifecycle Old dashboard container is destroyed when new dashboardId is given

Link to Jenkins

Standard Out

Failed Tests Reporter:
  - Test has not failed recently on tracked branches

Stack Trace

Error: Timed out in waitForNextUpdate after 1000ms.
    at Object.waitForNextUpdate (/var/lib/jenkins/workspace/elastic+kibana+pipeline-pull-request/kibana/node_modules/@testing-library/react-hooks/lib/core/asyncUtils.js:102:13)
    at Object.<anonymous> (/var/lib/jenkins/workspace/elastic+kibana+pipeline-pull-request/kibana/src/plugins/dashboard/public/application/hooks/use_dashboard_app_state.test.tsx:167:5)

---

Metrics [docs]

✅ unchanged

History

• 💚 Build #162163 succeeded f174933
• 💔 Build #161696 failed 1468fc9
• 💚 Build #161528 succeeded 5112efc
• 💚 Build #161184 succeeded a30ebb6

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

[simianhacker]

LGTM

[kibanamachine]

💔 Backport failed

Status	Branch	Result
❌	7.x	Commit could not be cherrypicked due to conflicts

To backport manually run:
node scripts/backport --pr 115103