release-24.1: sql: support DEFAULT expressions for routine parameters

[blathers-crl]

Backport 2/2 commits from #121082 on behalf of @yuzefovich.

/cc @cockroachdb/release

---

This commit adds support for DEFAULT expressions for routine parameters.
Routines can be declared with default values for some or all input
arguments. The default values are inserted whenever the routine is
called with insufficiently many actual arguments. Since arguments can
only be omitted from the end of the actual argument list, all
parameters after a parameter with a default value have to have default
values as well. For procedures additionally no OUT parameters are
allowed after the first input parameter with the DEFAULT expression. The
DEFAULT expression has to be coercible to the argument type of the
parameter.

Given that presence of DEFAULT expressions changes the overload
resolution, we need to include these into FunctionSignature proto. The
overload resolution logic has also been adjusted to try omitting some of
the input types for comparison (when applicable). In particular, UDF
dependency tracking for memo metadata has been extended to store the
"invocation signature" in addition to the overload itself given that
input types of the latter might now be different from the former.

In order to correctly track dependencies during schema changes, we
always serialize the DEFAULT expressions after having them type-checked.

Fixes: #100962.

Release note (sql change): DEFAULT expressions for input parameters of
user-defined functions and stored procedures are now supported.

---

Release justification: important new functionality.

[blathers-crl]

Thanks for opening a backport.

Please check the backport criteria before merging:

• Backports should only be created for serious
  issues or test-only changes.
• Backports should not break backwards-compatibility.
• Backports should change as little code as possible.
• Backports should not change on-disk formats or node communication protocols.
• Backports should not add new functionality (except as defined
  here).
• Backports must not add, edit, or otherwise modify cluster versions; or add version gates.
• All backports must be reviewed by the owning areas TL and one additional
  TL. For more information as to how that review should be conducted, please consult the backport
  policy.

If your backport adds new functionality, please ensure that the following additional criteria are satisfied:

• There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
• The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
• New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters. State changes must be further protected such that nodes running old binaries will not be negatively impacted by the new state (with a mixed version test added).
• The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.
• Your backport must be accompanied by a post to the appropriate Slack
  channel (#db-backports-point-releases or #db-backports-XX-X-release) for awareness and discussion.

Also, please add a brief release justification to the body of your PR to justify this
backport.

[blathers-crl]

Your pull request contains more than 1000 changes. It is strongly encouraged to split big PRs into smaller chunks.

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}

[cockroach-teamcity]

This change is 

[DrewKimball]

Reviewed 22 of 22 files at r1, 43 of 43 files at r2, all commit messages.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @fqazi, @mgartner, and @rafiss)