[Rest Api Compatibility] Typed TermLookups

[pgomulka]

Previously removed in #46943
parsing type field in term lookup is now possible with rest
compatible api. The type field is ignored

relates main meta issue #51816
relates type removal meta issue #54160

• Have you signed the contributor license agreement?
• Have you followed the contributor guidelines?
• If submitting code, have you built your formula locally prior to submission with gradle check?
• If submitting code, is your pull request against master? Unless there is a good reason otherwise, we prefer pull requests against master and will backport as needed.
• If submitting code, have you checked that your submission is for an OS and architecture that we support?
• If you are submitting this code for a class then read our policy for that.

[elasticmachine]

Pinging @elastic/es-core-infra (Team:Core/Infra)

[pgomulka]

this PR should also fix 'roles/30_prohibited_role_query/Test use prohibited query inside role query',
this test sends

security.put_role: name: "role" body: "{\n \"cluster\": [\"all\"],\n \"indices\": [\n {\n \"names\"\ : \"index\",\n \"privileges\": [\"all\"],\n \"query\" : {\n \ \ \"terms\" : { \"field\" : { \"index\" : \"_index\", \"type\" : \"_type\"\ , \"id\" : \"_id\", \"path\" : \"_path\"} }\n }\n }\n ]\n}\n" 

and should simply fail validation. However it fails on parsing a type field.
The reason is that, the validation is done in a transport layer.
https://github.com/elastic/elasticsearch/blob/master/x-pack/plugin/security/src/main/java/org/elasticsearch/xpack/security/action/role/TransportPutRoleAction.java#L46

Ideally we should have the validation in the rest layer I think. Upon the creation of RoleDescriptor - would be able to parametrise the parser with a RestApiVersion

The alternative would be to serialise a RestApiVersion in PutRoleRequest and perform the validation as it is in transport layer.

[romseygeek]

LGTM