release-23.2: backupccl: replace UDT IDs within routine bodies and views

[blathers-crl]

Backport 1/1 commits from #116656 on behalf of @DrewKimball.

/cc @cockroachdb/release

---

During a database RESTORE, it is necessary to replace descriptor IDs
from the old database with those from the new. Previously, we forgot
to do this rewrite for UDT IDs in routine bodies and views. This would
prevent using a database RESTORE with a user-defined function, stored
procedure, or view, that referenced a user-defined type. This patch
adds the needed rewrite logic and expands existing tests.

Fixes #116653

Release note (bug fix): Fixed a bug that prevented database RESTORE when
the database contained a view or routine that referenced a user-defined
type in the body string. For views, this bug was introduced in v20.2, when
UDTs were introduced. For routines, this bug was introduced in v22.2, when
UDFs were introduced.

---

Release justification: bug fix for broken functions after restore

[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.

[cockroach-teamcity]

This change is 

[mgartner]

Reviewed 6 of 6 files at r1, all commit messages.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @rafiss)

[DrewKimball]

Test failure is an unrelated timeout.