Add explicit automatic module name configuration.

[vbabanin]

Description :

Some modules rely on the publish.gradle file to generate the Automatic Module Name in the manifest, based on the groupName and archivesBaseName of the project. However, the archivesName contains hyphens that are not valid according to the Java Language Specification.

As a result, all Automatic Module Names are now explicitly specified in each build.gradle file:

org.mongodb.mongodb-driver-kotlin-coroutine is renamed to org.mongodb.driver.kotlin.coroutine
org.mongodb.mongodb-driver-kotlin-sync is renamed to org.mongodb.driver.kotlin.sync
org.mongodb.bson-kotlin is renamed to org.mongodb.bson.kotlin
org.mongodb.bson-kotlinx is renamed to org.mongodb.bson.kotlinx
org.mongodb.mongo-scala-driver is renamed to org.mongodb.driver.scala
org.mongodb.mongo-scala-bson is renamed to org.mongodb.bson.scala

JAVA-5213
JAVA-5202

[jyemin]

Should we remove Automatic-Module-Name configuration from publish.gradle entirely since it's rarely correct (bson is the only module without a hyphen, and driver-legacy should not have a module name)?

[jyemin]

Static checks are failing.

[vbabanin]

Should we remove Automatic-Module-Name configuration from publish.gradle entirely since it's rarely correct (bson is the only module without a hyphen, and driver-legacy should not have a module name)?

Agree, I've removed the Automatic-Module-Name configuration from publish.gradle, as it indeed seems unnecessary. Thank you!
With explicit naming in each build.gradle, it might be worth considering adding a validation check in publish.gradle after projects evaluation stage to ensure Automatic-Module-Name's are correctly specified and not overlooked if we have added a new module.

[rozza]

LGTM

[jyemin]

LGTM