Monitoring data can now be stored in `metrics-*` patterns when collected through elastic-agent. [Our documentation](https://www.elastic.co/guide/en/kibana/current/monitoring-data.html) recommends to use the `monitoring_user` role to view the data in Stack Monitoring application but that role does not have permissions to read from the metrics pattern.

`monitoring_user` should be allowed the same permissions on `metrics-*` as `.monitoring-*`
x-pack/plugin/core/src/test/java/org/elasticsearch/xpack/core/security/authz/store/ReservedRolesStoreTests.java
fieldPermissionsCache
            );
        assertThat("For " + iac, iac.hasIndexPermissions(TestRestrictedIndices.SECURITY_MAIN_ALIAS), is(false));
        assertThat("For " + iac, iac.hasIndexPermissions(internalSecurityIndex), is(false));
        assertTrue(superuserRole.indices().check(SearchAction.NAME));
        assertFalse(superuserRole.indices().check("unknown"));
        assertThat(superuserRole.runAs().check(randomAlphaOfLengthBetween(1, 30)), is(true));
        
        assertThat(
            superuserRole.indices()
                .allowedIndicesMatcher(randomFrom(GetAction.NAME, IndicesStatsAction.NAME))
                .test(mockIndexAbstraction(TestRestrictedIndices.SECURITY_MAIN_ALIAS)),
            is(true)
        );
        assertThat(
            superuserRole.indices()
                .allowedIndicesMatcher(randomFrom(GetAction.NAME, IndicesStatsAction.NAME))
                .test(mockIndexAbstraction(internalSecurityIndex)),
            is(true)
        );
        
        assertThat(
            superuserRole.indices()
                .allowedIndicesMatcher(randomFrom(IndexAction.NAME, DeleteIndexAction.NAME))
                .test(mockIndexAbstraction(TestRestrictedIndices.SECURITY_MAIN_ALIAS)),
            is(false)
        );
        assertThat(
            superuserRole.indices()
                .allowedIndicesMatcher(randomFrom(IndexAction.NAME, DeleteIndexAction.NAME))