Migrate to Gradle version catalogs for configuration cache compatibility

[fglock]

Summary

This PR migrates the project from the old dependency update plugins to Gradle Version Catalogs, which are fully compatible with Gradle's configuration cache.

Changes

• Removed incompatible plugins: and
• Added configuration cache compatible plugin:
• Created version catalog: for centralized dependency management
• Updated build.gradle: All dependencies now use version catalog references (e.g., libs.asm, libs.junit.jupiter.api)
• Updated Configure.pl: Changed from useLatestVersions to versionCatalogUpdate command
• Updated .gitignore: Allow tracking of libs.versions.toml
• Moved documentation: DEPENDENCY_UPDATES.md → dev/design/DEPENDENCY_UPDATES.md with updated instructions

Benefits

✅ Configuration cache fully enabled - No need to disable features or use --no-configuration-cache flag
✅ Cleaner dependency management - All versions centralized in one TOML file
✅ Type-safe references - IDE autocomplete for dependencies
✅ Modern best practice - Gradle's recommended approach for dependency management
✅ Easier updates - Simple command: ./gradlew versionCatalogUpdate

Testing

• ✅ Build successful with configuration cache enabled
• ✅ All tests pass
• ✅ Version catalog update task works correctly
• ✅ Configure.pl --upgrade works with new command

Usage

# Check and update dependencies
./gradlew versionCatalogUpdate

# Interactive mode
./gradlew versionCatalogUpdate --interactive

# Format version catalog
./gradlew versionCatalogFormat

See dev/design/DEPENDENCY_UPDATES.md for complete documentation.