ci: add retry logic for Maven Central 403 errors

[saurabhjain1592]

Summary

• Add retry loops (3 attempts with 30-60s delays) to all Maven commands
• Add -U flag to force updates and bypass cached failures
• Remove Maven cache from setup-java (caching was contributing to issues)
• Add explicit settings.xml configuration for credentials

Problem

GitHub Actions runners are intermittently getting 403 Forbidden errors from Maven Central (repo.maven.apache.org). This appears to be rate limiting or IP blocking from Maven Central's side.

Solution

1. Retry logic: Each Maven command now retries up to 3 times with delays between attempts
2. Force updates: Added -U flag to force Maven to check for updates
3. No caching: Removed Maven cache from setup-java action to avoid stale cached data
4. Explicit settings: Added settings.xml configuration inline

Test Plan

• Trigger release workflow with new tag
• Verify retry logic works on transient failures