refactor(config): improve startup errors and remove inactive assertions

[bladehan1]

What does this PR do?

• Replace selected startup IllegalArgumentException failures with TronError(PARAMETER_INIT).
• Remove selected historical Java assertions that are inactive under the default production JVM configuration.
• Preserve the assertions in the EthereumJ-derived TrieImpl and the Besu-derived Blake2bfMessageDigest implementations.
• Add focused unit and integration tests for the affected configuration error paths.
• Remove two tracked 0-byte Java placeholder files from chainbase.

Why are these changes required?

The selected failures are parameter initialization errors. Classifying them with PARAMETER_INIT makes startup failures consistent while preserving their messages and exit behavior.

The assertion cleanup is limited to historical java-tron code where the assertions are inactive by default. Assertions in TrieImpl are retained because its core implementation is derived from EthereumJ and the checks document internal node-type invariants. The Besu-derived Blake2bf assertion is retained for the same upstream-maintenance reason. Keeping these assertions avoids unnecessary divergence from their source implementations; replacing them with production runtime checks, if required, should be evaluated separately.

The two tracked placeholder files are empty and have no source references. Their deletion is moved here so the CI-only PR remains limited to workflow changes.

This PR has been tested by:

• Unit tests:
  • ./gradlew :common:test --tests org.tron.core.config.args.CommitteeConfigTest
  • ./gradlew :framework:test --tests org.tron.core.config.args.ArgsTest
  • ./gradlew -g /private/tmp/java-tron-gradle-home :framework:test --tests org.tron.core.tire.TrieTest
• Coverage reports:
  • ./gradlew :common:jacocoTestReport :framework:jacocoTestReport
  • Verified zero missed instructions for CommitteeConfig.java:166 and Args.java:1048,1092.
• Checkstyle:
  • ./gradlew :framework:checkstyleTest
• Whitespace validation:
  • git diff --check

Follow up

Other startup failures and any replacement of upstream-derived assertions with explicit runtime checks should be evaluated separately according to their semantics and performance impact.

Extra details

• Valid configuration and Trie behavior are unchanged.
• No protocol, database, network, or performance impact is expected.
• TrieImpl and Blake2bfMessageDigest are excluded from the assertion-removal scope.