Reporting Collation - deterministic attribute and Merge statement

[priyanshi-yb]

Describe the changes in this pull request

1. Reporting deterministic option (either true or false) as it is completely not supported in COLLATION object from PG. https://yugabyte.atlassian.net/browse/DB-14236
2. Reporting MERGE statement as its >=PG15 feature. https://yugabyte.atlassian.net/browse/DB-14222

Describe if there are any user-facing changes

Added feature in Unsupported Feature for Deterministic attribute in collation

Added feature for DMLs having MERGE statement -

How was this pull request tested?

added unit and end-to-end tests

Does your PR have changes that can cause upgrade issues?

Component	Breaking changes?
MetaDB	No
Name registry json	No
Data File Descriptor Json	No
Export Snapshot Status Json	No
Import Data State	No
Export Status Json	No
Data .sql files of tables	No
Export and import data queue	No
Schema Dump	No
AssessmentDB	No
Sizing DB	No
Migration Assessment Report Json	No
Callhome Json	No
YugabyteD Tables	No
TargetDB Metadata Tables	No

[sanyamsinghal]

How about naming the issue as Nondeterministic Collation

As per the docs - 'A collation is either deterministic or nondeterministic.'

[priyanshi-yb]

We can't rename the issue as Non-deterministic collation as we are not reporting the non-deterministic one only, we are reporting both the cases if deterministic or nondeterministic, as the deterministic option with collation is completely not supported in YB so it errors out if it is true even

CREATE COLLATION .... (..., deterministic = true);

[sanyamsinghal]

oh ok, what is the default if nothing is provided?

[priyanshi-yb]

its Deterministic by default