Add support for CORRESPONDING option in set operations

[ebyhr]

Description

Add support for CORRESPONDING option in set operations.
The option matches columns by name instead of by position:

SELECT * FROM (VALUES (1, 'alice')) AS t(id, name)
UNION ALL CORRESPONDING
SELECT * FROM (VALUES ('bob', 2)) AS t(name, id);

 id | name
----+-------
  1 | alice
  2 | bob
(2 rows)

The option is defined in SQL spec

<query expression body> ::=
    <query term> 
  | <query expression body>  UNION [ ALL | DISTINCT ]
      [ <corresponding spec>  ] <query term> 
  | <query expression body>  EXCEPT [ ALL | DISTINCT ]
      [ <corresponding spec>  ] <query term> 

<query term> ::=
    <query primary> 
  | <query term>  INTERSECT [ ALL | DISTINCT ]
      [ <corresponding spec>  ] <query primary> 

<corresponding spec> ::=
  CORRESPONDING [ BY <left paren>  <corresponding column list>  <right paren>  ]

P.508-509 in ISO_IEC_9075-2(E)_Foundation explains this option.

Release notes

## General
* Add support for the `CORRESPONDING` option in set operations. ({issue}`issuenumber`)

[ebyhr]

Changing to draft as I missed logic to handle different number of columns between left and right relations.

[github-actions]

This pull request has gone a while without any activity. Ask for help on #core-dev on Trino slack.

[ebyhr]

@martint Gentle reminder.

[martint]

Add examples for cases where the columns in the left and right table don't match exactly but have at least one common column.