[ILM] Searchable snapshot default "enabled" on cloud

[jloleysens]

Summary

Adds logic for turning searchable snapshots on by default on cloud.

How to test

1. Simulate being cloud by setting a value for xpack.cloud.id and xpack.cloud.deploymentUrl in kibana.dev.yml
2. Start Kibana on min basic license
3. Navigate to ILM plugin
4. Create a new policy
5. Enable the cold phase
6. Searchable snapshots should be on with a default value of found-snapshots for the snapshot repository
7. Repeat the above but with xpack.cloud.id and xpack.cloud.deploymentUrl unset (so non-cloud deployment)
8. Searchable snapshots should not be on when cold phase is turned on. When turning searchable snapshots on, the default value for snapshot repository should be empty

Checklist

• Unit or functional tests were updated or added to match the most common scenarios

[elasticmachine]

Pinging @elastic/es-ui (Team:Elasticsearch UI)

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: d745cd6

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
indexLifecycleManagement	251.2KB	251.4KB	+161.0B

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

[alisonelizabeth]

Code LGTM. I left one nit regarding the tests.

I also noticed I get a warning that no repositories are found, but found-snapshots is shown as the default. I imagine this is because I was not using a valid cloud id and deployment url, but just wanted to point this out.

[alisonelizabeth]

I noticed the test file is called edit_policy.test.ts. I'm not familiar with all the test cases here, but perhaps it should be renamed if we're testing both new and existing policies here?

[jloleysens]

This is a really good point. For now this lines up with the component/section name of the plugin. The semantics are not quite right, if you think it is worth it, would you mind opening an issue for this change? It seems like something that needs a bit of thought as to what it should be called and whether any restructuring/refactoring is required.

[jloleysens]

Thanks for the review @alisonelizabeth !

I also noticed I get a warning that no repositories are found, but found-snapshots is shown as the default. I imagine this is because I was not using a valid cloud id and deployment url, but just wanted to point this out.

Right, on-prem the field will not autocomplete to a non-existent snapshot repository. For the sake of the screenshot I hid the warning 😄