chore: Move to using the Maven Publish DSL

[mattcreaser]

• [x] PR title and description conform to Pull Request guidelines.

Issue #, if available:

Description of changes: Migrated publishing to use the publishing DSL. This is a pre-requisite to upgrading to Gradle 8+.

The publishing DSL adds scope information and publishes Gradle metadata by default. Although those are beneficial, they could potentially impact customers and should not be added in a minor version, so I've disabled/removed both of those. They can be enabled in a future major version release.

How did you test these changes? (Please add a line here how the changes were tested)

Documentation update required?

• [x] No
• [ ] Yes (Please include a PR link for the documentation update)

General Checklist

• [ ] Added Unit Tests
• [ ] Added Integration Tests
• [ ] Security oriented best practices and standards are followed (e.g. using input sanitization, principle of least privilege, etc)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[mattcreaser]

Note: the one difference I've noted with this PR is that it adds the Kotlin standard library as a dependency to all poms, specifically <artifactId>kotlin-stdlib-jdk8</artifactId>.

I am not actually sure why it wasn't being added before since the Kotlin plugin adds it to all projects so it always has been a dependency. Looking into whether there is any problem here.

[mattcreaser]

After some additional testing I don't believe there is any downside to this additional dependency being added. If app is running on JDK < 26 it does not add a requirement for desugaring unless we invoke one of the JDK8 APIs, which already would have been requiring desugaring previously.