[FLINK-33009][release] Disable binary compatibility check in master branch and only enable it in the release branch

[WencongLiu]

What is the purpose of the change

Disable binary compatibility check in master branch and only enable it in the release branch.

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): (no)
• The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
• The serializers: (no)
• The runtime per-record code paths (performance sensitive): (no)
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
• The S3 file system connector: (no)

Documentation

• Does this pull request introduce a new feature? (no)
• If yes, how is the feature documented? (not applicable)

[flinkbot]

CI report:

• e634566487438269e995514720d36fbc58ad5a2c Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run azure re-run the last Azure build

[WencongLiu]

I've tested the modified update_japicmp_configuration.sh and it could work well.