release-22.2: parser: add QUERY to bare_label_keyword

[blathers-crl]

Backport 1/1 commits from #97041 on behalf of @ZhouXing19.

/cc @cockroachdb/release

---

As revealed by #84309, some keywords not added to bare_label_keywords in sql.y make the SELECT ... <keyword> statement error out, which is not compatible with postgres. This commit is to add the QUERY keyword per a support ticket. We're not adding the whole unreserved_keyword list here as having some of them in bare_label_keyword, such as DAY, brings reduce errors.

Postgres:

postgres=# select substring('stringstringstring',1,10) query;
   query
------------
 stringstri
(1 row)

CRDB:

root@localhost:26257/defaultdb> select substring('stringstringstring',1,10)  query;
invalid syntax: statement ignored: at or near "query": syntax error
SQLSTATE: 42601
DETAIL: source SQL:
select substring('stringstringstring',1,10)  query
                                             ^

informs #84309

Release Note(bug fix): fixed the syntax error for SELECT ... QUERY (without AS) statement.

---

Release justification: bug fix

[blathers-crl]

Thanks for opening a backport.

Please check the backport criteria before merging:

• Patches should only be created for serious issues or test-only changes.
• Patches should not break backwards-compatibility.
• Patches should change as little code as possible.
• Patches should not change on-disk formats or node communication protocols.
• Patches should not add new functionality.
• Patches must not add, edit, or otherwise modify cluster versions; or add version gates.

If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.

• There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
• The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
• New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
• The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

• What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
• Will this work in a cluster of mixed patch versions? Did we test that?
• If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

[cockroach-teamcity]

This change is