Use and export kotest-bom for kotest dependencies management

[Spikhalskiy]

micronaut-test-kotest5 now uses and exposes kotest-bom

Related PR into micronaut-platform: micronaut-projects/micronaut-platform#901
Closes #843

[CLAassistant]

All committers have signed the CLA.

[Spikhalskiy]

Ideally explicit versions should be removed from

managed-kotest-assertions-core-jvm = { module = "io.kotest:kotest-assertions-core-jvm", version.ref = "managed-kotest" }
managed-kotest-runner-junit5-jvm = { module = "io.kotest:kotest-runner-junit5-jvm", version.ref = "managed-kotest" }

and

junit-jupiter-api = { module = "org.junit.jupiter:junit-jupiter-api", version.ref = "managed-junit" }
junit-jupiter-engine = { module = "org.junit.jupiter:junit-jupiter-engine", version.ref = "managed-junit" }
junit-jupiter-params = { module = "org.junit.jupiter:junit-jupiter-params", version.ref = "managed-junit" }

above it.

But when I try to do that I get

* What went wrong:
Could not determine the dependencies of task ':micronaut-test-bom:build'.
> Could not create task ':micronaut-test-bom:assemble'.
   > Could not create task ':micronaut-test-bom:generateCatalogAsToml'.
      > A dependency constraint was added on 'io.kotest:kotest-assertions-core-jvm' without a version. This is invalid: a constraint must specify a version.

I guess these constraints are getting added by an internal micronaut tooling ("io.micronaut.build.internal.bom" plugin?). But the message doesn't have enough info to easily untangle this without tracing back the source of the message. I didn't put time into figuring it out yet, so I left it as-is for now looking at the fact that it already was done for junit.

[melix]

Can you move the managed-kotest entries back to where they were? They are intentionally grouped by managed-.

Thanks

[Spikhalskiy]

@melix done. I moved them into "managed-by-boms" group because I was going to drop the explicit specification of the version, but wasn't able to do that as described above. Moved them back.

[melix]

No, please keep them as is. Do not rename them as it's a breaking change. We use conventions, and these lead to properties in BOM files, or type-safe accessors in catalogs. Any change in the name is a breaking change. Thanks!

Update: sorry I thought you renamed the aliases, realizing you didn't :)

[timyates]

Thanks for this @Spikhalskiy 👍