Add support for CALL in procedural languages

[lukaseder]

An essential piece of functionality inside of stored functions and procedures (#9190) is the standard SQL <call statement> and by consequence <routine invocation> support, which helps compose procedural routines for greater reusability.

The various syntaxes differ greatly, e.g.

Standard SQL (Db2, HSQLDB, MariaDB, MySQL, PostgreSQL)

'CALL' routineName '(' argument { ',' argument } ')'

Where an argument can be different things, including a named argument of the form parameterName '=>' value

Firebird

'EXECUTE PROCEDURE' routineName '(' argument { ',' argument } ')' [ 'RETURNING_VALUES' argument { ',' argument } ]

Oracle

routineName '(' argument { ',' argument } ')'

SQL Server

'EXEC' routineName argument { ',' argument }

Support will be added in:

• Db2
• Firebird
• HSQLDB
• Informix
• MariaDB
• MySQL
• Oracle
• PostgreSQL
• SQL Server

Postponed support:

• H2 (is it even possible? Seems tricky)
• HANA
• Teradata (all of Teradata's procedural language needs to be supported eventually)

And, as always

• In the parser

Additional features:

• Generated procedures should offer a way to turn themselves into CALL statements #11363 Turn a generated Routine into a CALL statement expression
• Make CALL a Query as in many dialects, it's a top-level, executable statement. This will be a prerequisite for Support parsing the JDBC escape syntax { call ... } #11415

Out of scope (for now):

• Support named and defaulted parameters in the API and parser
• Some dialects (e.g. BigQuery) require qualification for their procedures in CALL. Can we do that automatically?
• Meta lookups

The various syntaxes for capturing OUT parameters will be explored as well

---

Related but not the same: #3426, though if CALL was made an executable Query, then we might not need #3426 anymore.