SQL Server Signal table Id mismatch [DBZ-8753]

Migrated from [DBZ-8753](https://issues.redhat.com/browse/DBZ-8753)

h2. What Debezium connector do you use and what version?

I'm using the SQL Server Connector version 3.0.6
h2. What behavior do you expect?

When the Signal table have a 'uniqueidentifier' Id type the request should match the one from the Kafka topic.
h2. What behavior do you see?

What happens is the window is ignored due to casing with the message: 
{code:java}
Received request to open window with id = '691816A5-9E71-4BCB-9569-9D679E09E47B', expected = '691816a5-9e71-4bcb-9569-9d679e09e47b', request ignored

Received request to close window with id = '691816A5-9E71-4BCB-9569-9D679E09E47B', expected = '691816a5-9e71-4bcb-9569-9d679e09e47b', request ignored{code}
A workaround is to use another column type, but even after changing the column type new incremental requests do not work (this may be due offsets).
h2. Do you see the same behaviour using the latest released Debezium version?

Yes

No source files or tests are named. Start by reproducing the SQL Server Connector 3.0.6 case with a uniqueidentifier Signal table and compare the Signal table ID with the Kafka topic request; done means open and close window requests match despite casing, and incremental requests still work after changing the column type.

Written by the indexing model from the issue text.