Keep the publish credentials on Maven 3.10
The publish job fails with a 401 since the runner image moved to Maven 3.10.0 (run 38124855884, after #205). Maven 3.10 offers the credentials of server central only to repo.maven.apache.org, and the upload goes to central.sonatype.com. -Dmaven.repository.credentialScope=id matches the server by id again, as Maven's warning suggests. Checked against a local listener on 3.9.16 and 3.10.0; the proof is the publish run after the merge.
Summary by cubic
Fixes the Maven publish job returning 401 because Maven 3.10 limits the central server credentials to repo.maven.apache.org, while artifacts upload to central.sonatype.com.
Adds -Dmaven.repository.credentialScope=id so the server is matched by id again. Maven 3.9 ignores the property, so older runners are unaffected.