Remove enableGenerateCompiledEndpointRules entries from all customization.config files

[S-Saranya1]

Motivation and Context

This PR is part of a series to enable compiled endpoint rules for all services. Compiled endpoint rules are already enabled for 344 services via explicit "enableGenerateCompiledEndpointRules": true entries in their customization.config files. Once the default is flipped to true (in a follow-up PR), these entries become redundant. This PR removes them proactively to clean up the configs.

This PR is part of 3 cleanup PRs, other followup PRs:

• Cleanup PR: Removes the flag entirely from codegen, deletes the old interpreted code path, and merges the rules2 package into rules
• Service changes PR: Migrates STS/S3 source code off deprecated internal classes

Modifications

• Removed "enableGenerateCompiledEndpointRules": true from 344 service customization.config files under services/

Testing

• Verified zero remaining references to enableGenerateCompiledEndpointRules in service configs

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

• I confirm that this pull request can be released under the Apache 2 license

[S-Saranya1]

Note: Some tests are failing in CI because removing the flags in this PR causes the logic to fall back to false and use the old interpreted path. Some tests were written specifically for the compiled path (importing classes like RuleUrl, RuleResult that only exist in the compiled path), so they fail when the interpreted path is used. This will resolve once the next PR lands that changes the codegen logic and makes the compiled path the only path. This PR is merging to a feature branch and will be followed up with the subsequent PRs.