chore: increase central-publishing-maven-plugin waitMaxTime to 3600s

[jamespfaulkner]

Summary

• Increases the central-publishing-maven-plugin waitMaxTime used by release.yml from the default 1800s (30 min) to 3600s (60 min).
• The 4.1.9 release job's release:perform step hit the default timeout waiting for Sonatype Central to finish publishing the waggle-dance-rpm deployment — but the deployment actually succeeded a few minutes later (confirmed via Maven Central metadata: all 4.1.9 module artifacts, including waggle-dance-rpm, are live). The release itself was unaffected; only the GitHub Actions job reported a false failure.
• Must be passed via -Darguments since release:perform forks a separate deploy build for the actual publish step — a bare -DwaitMaxTime on the outer command wouldn't reach it.

Test plan

• Confirmed the timeout value: plugin's plugin.xml shows waitMaxTime default-value 1800, matching the exact ~30 min gap between the 4.1.9 deployment upload finishing and the job timing out.
• Confirmed 4.1.9 published successfully despite the job failure (all module artifacts, .rpm, signatures, and checksums present on Maven Central; maven-metadata.xml shows 4.1.9 as <latest>/<release> with a lastUpdated timestamp after the timeout).
• Next release run will confirm the job completes without hitting the timeout (can't be verified until the next workflow_dispatch of release.yml).

🤖 Generated with Claude Code