Elasticsearch version: 7.14.0-SNAPSHOT
OS version Windows 10:

Description of the problem including expected versus actual behavior:

I've noticed while running YML tests against the .NET client some have started failing for 7.14.0-SNAPSHOT due to the inclusion of geoip_databases in results from the _cat/* APIs ( for example, _cat/indices and _cat/shards), which the assertions are not expecting. It looks like this was recently re-enabled in this PR and I wanted to see if this should be treated as a system index?

Slightly more problematic is that a request to GET /_alias receives an exception response:

{
    "error": {
        "root_cause": [
            {
                "type": "illegal_argument_exception",
                "reason": "Indices [.geoip_databases] use and access is reserved for system operations"
            }
        ],
        "type": "illegal_argument_exception",
        "reason": "Indices [.geoip_databases] use and access is reserved for system operations"
    },
    "status": 400
}

I would expect this to be excluded. The merge of this PR seems to be very close to the date when the tests started failing.

Steps to reproduce:

1. Start a new single-node cluster using the latest 7.14.0-SNAPSHOT (I pulled and ran the Docker image).
2. Send a GET /_alias request

Expect that this API should expand to open, closed and hidden indices but not system indices.