Use Proper query scope in CTE Materialization

[jaystarshot]

Fixes #21563.

Motivation and Context

Fixes an issue with cte refereneces referencing wrong ctes (sample examples mentioned in the issue). This was causing incorrect plans.
Each reference of the cte expands the same namedQuery, hence we can fix all these issues with normalization of that named query object

Contributor checklist

• Please make sure your submission complies with our development, formatting, commit message, and attribution guidelines.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.
• Final Prod Shadow test

Release Notes

Please follow release notes guidelines and fill in the release notes below.

== RELEASE NOTES ==

General Changes
* Fixed a bug in cte materialization which was causing incorrect plan generation in some cases

[jaystarshot]

This same issue will happen in CteInformationCollector (wrong reference count will increase), thinking about adding a new field called actualCtePath in CTEInformation. What do you think?

[mlyublena]

nit: you can use putIfAbsent

[jaystarshot]

Keeping same since its better that the ++ happens only if its new

[mlyublena]

nit: why do we convert the scope id to string?

[jaystarshot]

Just so that it is easier to debug and add tests, we can use hashCode but it becomes complicated

[jaystarshot]

SELECT (WITH test_base AS
       (
              SELECT colb
              FROM   (VALUES
                     (
                            1
                     )
                     ) AS temptable(colb)), test_cte AS
       (
              SELECT *
              FROM   test_base)SELECT *
FROM   test_cte ),
       (WITH test_base AS
       (
              SELECT text_column
              FROM   (VALUES
                     (
                            'Some Text',
                            9
                     )
                     ) AS t (text_column, number_column) ), test_cte AS
       (
              SELECT *
              FROM   test_base )SELECT *
FROM   test_cte )

Observed just one more extra edge case in prod where the definition of test_cte stays constant, but test_base undergoes changes, such as referencing a different column. In this case we are still considering both ctes to be the same.
Thinking how to fix this, because seems non trivial. Seems like just adding the set of referenced queries will work

[feilong-liu]

typo: Defination -> Definition