[Reporting] Deprecation text for the removal of xpack.reporting.index is wrong

[tsullivan]

Kibana version: 7.16

Elasticsearch version:

Server OS version:

Browser version:

Browser OS version:

Original install method (e.g. download page, yum, from source, etc.):

Describe the bug:

Steps to reproduce:

1. (Using 7.16) Use a custom xpack.reporting.index
2. View the deprecations in the Upgrade Assistant
3. Text is wrong for Setting "xpack.reporting.index" is deprecated:

   kibana/x-pack/plugins/reporting/server/config/index.ts

   Lines 38 to 47 in 1c5317f

   	correctiveActions: {
   	manualSteps: [
   	i18n.translate('xpack.reporting.deprecations.reportingIndex.manualStepOne', {
   	defaultMessage: `If you rely on this setting to achieve multitenancy you should use Spaces, cross-cluster replication, or cross-cluster search instead.`,
   	}),
   	i18n.translate('xpack.reporting.deprecations.reportingIndex.manualStepTwo', {
   	defaultMessage: `To migrate to Spaces, we encourage using saved object management to export your saved objects from a tenant into the default tenant in a space.`,
   	}),
   	],
   	},

Expected behavior:
Reports are not Space-aware, and using Spaces doesn't resolve issues with multi-tenancy for Reporting.

The text should say something like, "Corrective actions: regenerate reports that need to be available for download in Kibana. You will not have access to reports that are stored in a custom index."

[elasticmachine]

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

[tsullivan]

cc @alexfrancoeur

[sscarduzio]

Are reports expected to be saved into respective spaces in the future? This would be very helpful.

[tsullivan]

Are reports expected to be saved into respective spaces in the future? This would be very helpful.

I'll defer this question to @alexfrancoeur and @sixstringcode

[sixstringcode]

@sscarduzio That's something we actually haven't discussed that I am aware of. I will look into the idea and make sure we discuss it in our planning conversations. Can you help provide a little more detail on how/why this would be useful for you?

[alexfrancoeur]

Sorry for the late reply here, circling back to the original deprecation warning. We'll likely want @kobelb's thoughts here as well, but I think we should aim for a descriptive and actionable deprecation warning. If needed, we can likely rope in our tech writing team for some thoughts on how best to craft this message.

What we choose to display also feels tightly coupled to this answer: #82020 (comment)

[tsullivan]

Closed via #114219