[Reporting] Add deprecation notice to the upgrade assistant

[jloleysens]

Summary

Continuation of #100130 and fix #81544

This contribution adds an integration with the deprecation service. The deprecation flags the new reporting policy and provides a "quick resolution" in the upgrade assistant which uses the new "PUT /deprecations" endpoint.

How to test

1. Start Kibana and ES, on basic license level
2. Make the following request against the ES:

curl --request PUT \
  --url 'http://localhost:9200/.reporting-*/_settings' \
  --header 'Authorization: Basic ZWxhc3RpYzpjaGFuZ2VtZQ==' \
  --header 'Content-Type: application/json' \
  --data '{
	"settings": {
		"index.lifecycle.name": null
	}
}'

3. Go the Upgrade Assistant (in code) and do the following:

diff --git i/x-pack/plugins/upgrade_assistant/public/plugin.ts w/x-pack/plugins/upgrade_assistant/public/plugin.ts
index 4cffd40faf3..701eefc33b6 100644
--- i/x-pack/plugins/upgrade_assistant/public/plugin.ts
+++ w/x-pack/plugins/upgrade_assistant/public/plugin.ts
@@ -58,7 +58,7 @@ export class UpgradeAssistantUIPlugin implements Plugin {
           coreSetup,
           params,
           kibanaVersionInfo,
-          readonly
+          false
         );
 
         return () => {

4. Go the upgrade assistant in the UI and see the deprecation warning there

Screenshots

Please note: the current Upgrade Assistant UI is subject to a lot of change prior to 8.0.

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

[elasticmachine]

Pinging @elastic/kibana-app-services (Team:AppServices)

[elasticmachine]

Pinging @elastic/kibana-reporting-services (Team:Reporting Services)

[jloleysens]

@elasticmachine merge upstream

[jloleysens]

@elasticmachine merge upstream

[jloleysens]

@elasticmachine merge upstream

[jloleysens]

@elasticmachine merge upstream

[jloleysens]

@elasticmachine merge upstream

[tsullivan]

This policy is automatically created in a newly set up environment, right? I'm wondering what is the best way to test this for reviewers. Can you add a writeup of how to test this PR?

I'm not sure if it would help, but perhaps it is handy to use our es_archive called reporting/archived_reports. The index created from this archive does not come with the new built-in policy. However, there are only archived reports belonging to test_user.

> node scripts/es_archiver.js \
  --config x-pack/test/functional/config.js \
  load x-pack/test/functional/es_archives/reporting/archived_reports \
  --es-ca config/cert-bundle/ca/ca.crt \ #  (use this example if you run Elasticsearch over HTTPS)
  --es-url https://elastic:changeme@localhost:9200 \ # (change to http if needed)
  --kibana-url http://elastic:changeme@localhost:5601 # (change to http if needed)

Edit: edited my thoughts

[jloleysens]

@elasticmachine merge upstream

[jloleysens]

Great points @tsullivan ! I'll update the PR description with that information. The way I was testing this locally is by running the following request against the cluster:

curl --request PUT \
  --url 'http://localhost:9200/.reporting-*/_settings' \
  --header 'Authorization: Basic ZWxhc3RpYzpjaGFuZ2VtZQ==' \
  --header 'Content-Type: application/json' \
  --data '{
	"settings": {
		"index.lifecycle.name": null
	}
}'

We also have API integration tests for creating a situation where reporting indices are "unmanaged":

kibana/x-pack/test/reporting_api_integration/services/scenarios.ts

Line 184 in 473b6aa

const makeAllReportingIndicesUnmanaged = async () => {

Granted, this does not test all possible permutations of reporting indices out there (maybe some are already set up to be managed by an index template), but it does simulate the "default" state you would end up in (no index lifecycle policy set on reporting indices).

[kibanamachine]

💚 Build Succeeded

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

Metrics [docs]

✅ unchanged

History

• 💚 Build #139674 succeeded 6c86593
• 💚 Build #138118 succeeded 342c7e5
• 💚 Build #137892 succeeded 2225b92
• 💔 Build #137760 failed 7251c4f
• 💚 Build #137168 succeeded 37e3583

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

[tsullivan]

LGTM

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	7.x

This backport PR will be merged automatically after passing CI.