[Index Management] Fix encoding issue on index details page

[yuliacech]

Summary

Fixes #166100

This PR adds a workaround fix for the new index details page when opening for index names with special characters, for example test_index%. Because of how encoding/decoding works, we can't use the index name as a part of the url like /indices/${indexName} (see for more details). Instead we have to pass the index name in a query parameter like `/indices/index_details?indexName=${indexName}. The downside of this workaround is that the url semantics doesn't reflect that the index name is mandatory for the page to work. Once #132600 is resolved, we should revert this workaround and use the index name as a url segment again.

Note for reviewers: The jest tests for this fix are part of #165705

How to test

1. Add xpack.index_management.dev.enableIndexDetailsPage: true to the file config/kibana.dev.yml to enable the new index details page
2. Navigate to Index Management and use the "create index" button
3. Type a name with special characters, for example test%
4. Click the new index name in the list and check that the details page and all tabs work
5. Also reload the page completely and check that the page still loads correctly

[yuliacech]

We need to extract these constants to a separate file in common folder so that it could be imported without increasing the bundle size.

[elasticmachine]

Pinging @elastic/platform-deployment-management (Team:Deployment Management)

[alisonelizabeth]

Great work! I'm happy we were able to find a temporary workaround for this 🎉

The downside of this workaround is that the url semantics doesn't reflect that the index name is mandatory for the page to work.

Does it make sense to add a check that the index was specified as a query param before making the request to fetch the index? We might also consider rendering a slightly different error message in that scenario. Here's the current behavior:

[yuliacech]

Thank you for the review, @alisonelizabeth! Great point about the empty index name, definitely adding a better error message for this case and will also check if I can prevent the unnecessary request as well.

[yuliacech]

I added a message when no index name is provided and stopped an unnecessary http request (d3591e6).

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 8064fa6

Failed CI Steps

• FTR Configs #41

Test Failures

• [job] [logs] FTR Configs #41 / serverless observability UI Observability Log Explorer Dataset Selector with installed integrations and uncategorized data streams when open on the integrations tab should display a list of installed integrations

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
indexManagement	605	606	+1

Async chunks

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

id	before	after	diff
indexManagement	601.6KB	601.3KB	-216.0B

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
indexManagement	33.1KB	33.6KB	+532.0B

History

• 💔 Build #161159 failed 820fb4a
• 💔 Build #161135 failed 8eba5d3
• 💛 Build #161077 was flaky 41debe7
• 💛 Build #160946 was flaky 15af942
• 💛 Build #160921 was flaky 4f94f82

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