[fix](fe) Route binlog format changes through validation

[hutiefang76]

What problem does this PR solve?

Issue Number: close #65383

Related PR: None

Problem Summary:

ALTER TABLE ... SET ('binlog.format'=...) was not recognized as a binlog configuration update. It fell through to the generic schema-change path and returned the ROW-binlog schema-change error before the existing immutable-format validation could run.

This change routes binlog.format through updateBinlogConfig(), where BinlogConfig.mergeFromProperties(..., false) already returns the specific unsupported format-change error.

Release note

Unsupported binlog.format changes now report the immutable binlog-format error instead of the generic ROW schema-change error.

Check List (For Author)

• Test

  • Regression test
  • Unit Test
    • AlterOperationsTest
    • SchemaChangeHandlerTest#testChangeBinlogFormatReportsBinlogError
    • ./build.sh --fe
  • Manual test
  • No need to test or manual test.

• Behavior changed:

  • No.
  • Yes. Only the error reported for unsupported binlog.format changes is corrected.

• Does this need documentation?

  • No.
  • Yes.

I used AI-assisted review during development. I verified the root cause, patch, tests, and build locally.

[hello-stephen]

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
3. What features were added. Why was this function added?
4. Which code was refactored and why was this part of the code refactored?
5. Which functions were optimized and what is the difference before and after the optimization?

[spaces-X]

binlog.need_historical_value seems to have the same routing gap as binlog.format. ModifyTablePropertiesOp.validate() treats it as a binlog property, and BinlogConfig.mergeFromProperties(..., false) explicitly rejects changing it, but checkBinlogConfigChange() still routes it through the generic schema-change path. Could we include PROPERTIES_BINLOG_NEED_HISTORICAL_VALUE here and add the parallel test?