### Description

The [Get API key information API](https://www.elastic.co/guide/en/elasticsearch/reference/master/security-api-get-api-key.html) can currently filter the returned keys by:
 * key id/name
 * keys owned by the calling user
 * keys owned by other users, by `realm_name` and `username`

Irrespective of the filtering used, both invalidated and expired (but not yet deleted) keys will be included in the response.
In the response, keys have the `invalidated` boolean property, as well as the `expiration` property that contains the UNIX timestamp past of which the key is no longer valid for authentication.

I propose we introduce a way for the API to support retrieving:
* only valid API keys (not return invalidated keys) - using a boolean request parameter
* keys not expired before a certain timestamp - using a timestamp parameter that defaults to "now" - also note that keys' experiation date is always checked against the local node's clock
x-pack/plugin/security/src/main/java/org/elasticsearch/xpack/security/authc/ApiKeyService.java
throw new IllegalArgumentException("cannot update invalidated API key [" + apiKeyId + "]");
        }
        boolean expired = apiKeyDoc.expirationTime != -1 && clock.instant().isAfter(Instant.ofEpochMilli(apiKeyDoc.expirationTime));
        if (expired) {
            throw new IllegalArgumentException("cannot update expired API key [" + apiKeyId + "]");
        }
        if (Strings.isNullOrEmpty(apiKeyDoc.name)) {
            throw new IllegalArgumentException("cannot update legacy API key [" + apiKeyId + "] without name");
        }
        if (expectedType != apiKeyDoc.type) {
            throw new IllegalArgumentException(
                "cannot update API key of type [" + apiKeyDoc.type.value() + "] while expected type is [" + expectedType.value() + "]"
            );
        }
    }
    /**
     * This method removes remote indices privileges from the given role descriptors
     * when we are in a mixed cluster in which some of the nodes do not support remote indices.
     * Storing these roles would cause parsing issues on old nodes
     * (i.e. nodes running with transport version before
     * {@link org.elasticsearch.transport.RemoteClusterPortSettings#TRANSPORT_VERSION_ADVANCED_REMOTE_CLUSTER_SECURITY_CCS}).
     */
    static Set<RoleDescriptor> maybeRemoveRemoteIndicesPrivileges(
        final Set<RoleDescriptor> userRoleDescriptors,
        final TransportVersion transportVersion,
        final String... apiKeyIds
    ) {
        if (transportVersion.before(TRANSPORT_VERSION_ADVANCED_REMOTE_CLUSTER_SECURITY_CCS)) {
            final Set<String> affectedRoles = new TreeSet<>();
            final Set<RoleDescriptor> result = userRoleDescriptors.stream().map(roleDescriptor -> {