We should not allow the user to configure index patterns that also match
rollup indices (either the index specified in the config, or previously
created jobs).

Matching against rollup indices will almost certainly lead to bad behavior,
because the expected fields in the user index won't exist in the rollup
(due to renaming).  It is also unlikely a user will want to match
against a rollup index.

For example, it is quite natural for a user to specify `metricbeat-*`
as the index pattern, and then store the rollups in `metricbeat-rolled`.
This will start throwing errors as soon as the rollup index is created
because the indexer will try to search it.

…arch

…arch