feat(sql-udf): introduce udf_binding_flag

[xzhseh]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

As titled, and this PR is a preparation for named sql udf support.

I've tried introducing a runtime binder, but the recursive nature of udf_context makes this approach seemingly impossible.

To KISS, I introduce a simple binding flag to prevent potential naming conflict, since we could ensure there will not be column name inside the body of sql udf. (i.e., every valid identifier in definition should be one of [parameter name / anonymous parameter index / function name])

e.g., the following syntax will be supported in next PR

create function mix_func(INT, a INT, INT) returns int language sql as 'select $1 + a + $3';

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• I have added test labels as necessary. See details.
• I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
• My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
• All checks passed in ./risedev check (or alias, ./risedev c)
• My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

• My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

[wangrunji0408]

LGTM