fix: query id for TERMINATE should be case insensitive

[big-andy-coates]

Description

fixes: #5003

The query id passed to TERMINATE <queryId> is currently case-sensitive. So, for example,

TERMINATE CSAS_A_0;

May work, but:

TERMINATE csas_a_0;

Won't.

CSAS and CTAS create queries with upper case ids. However, INSERT INTO creates mixed case queries, e.g. InsertQuery_3. Again, users must get the case right to terminate them.

SQL is meant to be case-insensitive by default! Hence this change switches terminate to be case-insensitive.

Testing done

Because the command topics of users will contain existing queries with query ids in upper and mixed case, we need to be a little careful any fix doesn't stop users from terminating historic queries or meaning restores leave previously terminated queries running. There is also another open PR that we need to ensure works with any change made here: #5002

To this end I went through the following steps, and ensured each worked, (this is also roughly the commit list):

1. I first made QueryId internally case-insensitive, but externally case-preserving, i.e. a queryId of ID and id would generate the same hash code and return true from equals, but we return ID and id from toString. This is the least invasive fix. I ran both the master branch and feat: speed up restarts by not building topologies for terminated queries #5002 to ensure this wouldn't cause any issues elsewhere in the code.
2. I updated RecoveryTest to have some terminates with the wrong case.
3. (added some tests to QueryId)
4. Changed the generation of queryIds to ensure they are always upper case - this means all new queries will have uppercase query ids. If all else fails, on the next breaking change release we can switch QueryId to be always uppercase.

It was not easily achievable to update QueryId to just uppercase its query id, as the text representation is used to, among other things, build the names for internal topics.

Reviewer checklist

• Ensure docs are updated if necessary. (eg. if a user visible feature is being added or changed).
• Ensure relevant issues are linked (description should include text like "Fixes #")

[spena]

lgtm

[JimGalasyn]

LGTM