release-25.1: opt/optbuilder: only re-type-check values rows for wildcard types

[blathers-crl]

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

/cc @cockroachdb/release

---

After #129706 we began type-checking expressions in Values operators again after building them. This is needed to update the resolved type if there was a RECORD-returning UDF, which cannot resolve its type until after it is built. However, this fix broke some other cases because the initial type-check can discard casts, causing the second time to result in a slightly different type (e.g. TIMESTAMP vs TIMESTAMPTZ). This commit fixes the oversight by only type-checking the second time if the previously resolved type was a wildcard type like AnyTuple, indicating that a concrete type could not be found on the first pass.

Fixes #137968

Release note (sql change): Fixed a bug existing only in pre-release versions of v25.1 which could cause unexpected errors during planning for VALUES expressions containing function calls with multiple overloads.

---

Release justification: narrows the scope of a previous fix to prevent regressions

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

[michae2]

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

[mgartner]

Nice fix!!