[BEAM-11747] Disable BeamJavaUdfCalcRule.

[ibzib]

A simple forward fix for concerns about the correctness of BeamJavaUdfCalcRule.

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Choose reviewer(s) and mention them in a comment (R: @username).
• Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

Post-Commit Tests Status (on master branch)

Lang	SDK	Dataflow	Flink	Samza	Spark	Twister2
Go		---		---		---
Java
Python				---		---
XLang				---		---

Pre-Commit Tests Status (on master branch)

---	Java	Python	Go	Website	Whitespace	Typescript
Non-portable
Portable	---		---	---	---	---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

[ibzib]

R: @amaliujia @apilloud
cc: @kennknowles

[ibzib]

Actually, it's probably better to just not add BeamJavaUdfCalcRule to the planner by default. That way we can still test the matching.

[apilloud]

I actually like everything here, this change will enable me to submit a compliance test covering BeamJavaUdfCalcRule inside Google.

[ibzib]

I actually like everything here, this change will enable me to submit a compliance test covering BeamJavaUdfCalcRule inside Google.

How can we test BeamJavaUdfCalcRule if it never matches anything though? For that reason I think it's better to go with #14009 and then remove BeamJavaUdfCalcRule from the default rules. That way all you have to do to test BeamJavaUdfCalcRule is add the rule.