[Reporting/New Platform Migration] Use a new config service on server-side

[tsullivan]

Part of #53898

This PR integrates the ReportingConfig service. based on a New-Platform schema, throughout server-side Reporting. This removes the biggest legacy dependency in Reporting.

Getting access to the config requires access to the ReportingCore object on the server.

async function getConfig(reportingCore: ReportingCore) {
   return await reportingCore.getConfig();
}

The getConfig function returns an object with a get method, and a kbnConfig object property that also has a get method. I'm using config.get() to read the Reporting config, and config.kbnConfig.get() to read the global Kibana config. The kbnConfig part is to keep the call signatures about the same as the legacy code, when reading the global config. For example, to get the server host name, the legacy call is server.config().get('server.host') and now it's: config.kbnConfig.get('server', 'host'). And it is also type-safe unlike the legacy calls.

Because the access is asynchronous, the code tries to strip the config out of the reportingCore object when passing down to other modules, such as routes registration. This is to avoid the need to convert those modules to asynchronous.

As part of the new accessor on the ReportingCore object, this PR also adds an accessor for the Elasticsearch service:

async function getElasticsearch(reportingCore: ReportingCore) {
  return await reportingCore.getElasticsearchService();
}

Summary of the changes:

• Remove legacy config code
• Add new config schema to NP Reporting plugin
• Change function signatures to accept the ReportingConfig object
• Change createJobFactory / executeJobFactory functions to be async
• For async functions that accept the ReportingCore object, don't pass the ElasticsearchServiceSetup API: use await reporting.getElasticsearchService() instead.
• Add createConfig$ to update defaults as needed, because config.set is not available anymore.

Todo

• [ ] Access path.data from New Platform API this is a TODO for after moving the code to NP
• Unit test for the new schema declaration
• Unit test for function createConfig$
• Unit test for validating the server host
• Unit test for random encryption key generation
• I18N for the modified files 🎉
• Make config.get() and config.kbnConfig.get() type-safe 🎉
• Resolution on comments about the disableSandbox code changes: https://github.com/elastic/kibana/pull/55882/files#r395927154

Checklist

Use strikethroughs to remove checklist items you don't feel are applicable to this PR.

• [ ] This was checked for cross-browser compatibility, including a check against IE11
• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• [ ] Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• [ ] This was checked for keyboard-only and screenreader accessibility

For maintainers

• This was checked for breaking API changes and was labeled appropriately
• [ ] This includes a feature addition or change that requires a release note and was labeled appropriately

[tsullivan]

The UI needs to be updated in-step with this change cc @joelgriffith

[elasticmachine]

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

[joelgriffith]

LGTM! Going to test this today and see how it all plays out.

[joelgriffith]

@elasticmachine merge upstream

[joelgriffith]

Smoke tests looking good. Will merge once CI is green

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 6151df8

History

• 💚 Build #35142 succeeded ad8269c
• 💔 Build #35066 failed b3ec447
• 💔 Build #34987 failed 6bcd58d
• 💚 Build #34977 succeeded dde6188615c29a38729a6aa637243c727b81b58b
• 💚 Build #34759 succeeded 44a94ce750d9438790a307e4f9d0601e9a10ba01

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

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 55882 or prevent reminders by adding the backport:skip label.

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 55882 or prevent reminders by adding the backport:skip label.

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 55882 or prevent reminders by adding the backport:skip label.

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 55882 or prevent reminders by adding the backport:skip label.

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 55882 or prevent reminders by adding the backport:skip label.

[kibanamachine]

Friendly reminder: Looks like this PR hasn’t been backported yet.
To create backports run node scripts/backport --pr 55882 or prevent reminders by adding the backport:skip label.

[tsullivan]

Reverted: #61075