[SPARK-50598][SQL] An initial, no-op PR which adds new parameters to already existing classes UnresolvedWith, CTERelationRef and CTERelationDef to enable later implementation of recursive CTEs.

[milanisvet]

What changes were proposed in this pull request?

PR adds new parameters to already existing classes UnresolvedWith, CTERelationRef and CTERelationDef to enable later implementation of recursive CTEs.

• Additional parameters are added in pattern matching cases in other files of mentioned classes as well.
• A large number of trivial changes in tests was required, due to new parameters introduced to the classes, which are also addressed in this PR.
• More information for reviewers can be found here: https://docs.google.com/document/d/1qcEJxqoXcr5cSt6HgIQjWQSqhfkSaVYkoDHsg5oxXp4/edit

Why are the changes needed?

Support for the recursive CTE.

Does this PR introduce any user-facing change?

No. RECURSIVE keyword is not introduced in this PR.

How was this patch tested?

The tests failing after the initial change were all in SQLQueryTestSuite, so this patch was tested by running this Test Suite.

Was this patch authored or co-authored using generative AI tooling?

No.

[MaxGekk]

@peter-toth Please, have a look at the PR.

[milanisvet]

@peter-toth Please, have a look at the PR.

We already contacted Peter and I don't think he will have time to review it. Could you have a look at it? This PR are only small no-op changes to enable later introduction to recursive CTEs.

[peter-toth]

I've just taken a quick look, and this PR seems to just extract some changes from my #40744 so I'm fine with these changes.

But @milanisvet , if you want to split the changes into smaller pieces then probably SPARK-24497 should be converted to an umbrella/epic ticket and the changes should be subtasks of it.

@cloud-fan, @dongjoon-hyun what is the preffered way of organizing the work?

[milanisvet]

@peter-toth thanks a lot for your comment. Let us then wait for @cloud-fan to answer the question about JIRA, so that I know if I should restructure it. After that, hopefully we can merge this.

[cloud-fan]

thanks, merging to master!

[cloud-fan]

Oh, I'll merge after the proper JIRA ticket is created.

[milanisvet]

JIRA subticket created, and the PR description is changed with the new JIRA ticket number @cloud-fan
Thanks again for approving :)