[Index Management] Error when a data stream contains a % character (dollar sign)

[yuliacech]

Kibana version:
Found on current master branch

Describe the bug:
After clicking on data stream name in the table, no flyout is shown and the app stops working.

Steps to reproduce:

1. Create a policy, an index template and a data stream with % character

commands in DevTools

PUT /_ilm/policy/my-data-stream-policy
{
  "policy": {
    "phases": {
      "hot": {
        "actions": {
          "rollover": {
            "max_size": "25GB"
          }
        }
      },
      "delete": {
        "min_age": "30d",
        "actions": {
          "delete": {}
        }
      }
    }
  }
}

PUT /_index_template/my-data-stream-template_1
{
  "index_patterns": [ "my-data-stream%*" ],
  "data_stream": { },
  "priority": 200,
  "template": {
    "settings": {
      "index.lifecycle.name": "my-data-stream-policy"
    }
  }
}

POST /my-data-stream%25/_doc/
{
  "@timestamp": "2020-12-06T11:04:05.000Z",
  "user": {
    "id": "vlb44hny"
  },
  "message": "Login attempt failed"
}

2. Navigate to Stack Management -> Index Management -> Data streams tab
3. Click on data stream name

Expected behavior:
Flyout is shown and the app is working

Screenshots (if relevant):

Errors in browser console (if relevant):

console errors

routing.ts:61 Uncaught URIError: URI malformed
    at decodeURIComponent (<anonymous>)
    at decodePathFromReactRouter (routing.ts:61)
    at DataStreamList (data_stream_list.tsx:159)
    at renderWithHooks (react-dom.development.js:16260)
    at updateFunctionComponent (react-dom.development.js:18347)
    at beginWork$1 (react-dom.development.js:20176)
    at HTMLUnknownElement.callCallback (react-dom.development.js:336)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:385)
    at invokeGuardedCallback (react-dom.development.js:440)
    at beginWork$$1 (react-dom.development.js:25780)
decodePathFromReactRouter @ routing.ts:61
DataStreamList @ data_stream_list.tsx:159
renderWithHooks @ react-dom.development.js:16260
updateFunctionComponent @ react-dom.development.js:18347
beginWork$1 @ react-dom.development.js:20176
callCallback @ react-dom.development.js:336
invokeGuardedCallbackDev @ react-dom.development.js:385
invokeGuardedCallback @ react-dom.development.js:440
beginWork$$1 @ react-dom.development.js:25780
performUnitOfWork @ react-dom.development.js:24695
workLoopSync @ react-dom.development.js:24671
performSyncWorkOnRoot @ react-dom.development.js:24270
(anonymous) @ react-dom.development.js:12199
unstable_runWithPriority @ scheduler.development.js:697
runWithPriority$2 @ react-dom.development.js:12149
flushSyncCallbackQueueImpl @ react-dom.development.js:12194
flushSyncCallbackQueue @ react-dom.development.js:12182
discreteUpdates$1 @ react-dom.development.js:24423
discreteUpdates @ react-dom.development.js:1438
dispatchDiscreteEvent @ react-dom.development.js:5881
react_devtools_backend.js:2273 The above error occurred in the <DataStreamList> component:
    in DataStreamList (created by Context.Consumer)
    in Route (created by IndexManagementHome)
    in Switch (created by IndexManagementHome)
    in div (created by EuiPanel)
    in EuiPanel (created by EuiPageContent)
    in EuiPageContent (created by IndexManagementHome)
    in main (created by EuiPageBody)
    in EuiPageBody (created by IndexManagementHome)
    in IndexManagementHome (created by Context.Consumer)
    in Route (created by AppWithoutRouter)
    in Switch (created by AppWithoutRouter)
    in AppWithoutRouter (created by App)
    in Router (created by App)
    in App
    in GlobalFlyoutProvider
    in ComponentTemplatesProvider
    in IndexSettingsProvider (created by MappingsEditorProvider)
    in StateProvider (created by MappingsEditorProvider)
    in MappingsEditorProvider
    in AppContextProvider
    in Provider
    in Provider
    in EuiContext (created by I18nContext)
    in PseudoLocaleWrapper (created by I18nProvider)
    in IntlProvider (created by I18nProvider)
    in I18nProvider (created by I18nContext)
    in I18nContext

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://fb.me/react-error-boundaries to learn more about error boundaries.

[elasticmachine]

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