Update sbt-multi-jvm to 0.6.0

[scala-steward-asf]

About this PR

📦 Updates com.typesafe.sbt:sbt-multi-jvm from 0.4.0 to 0.6.0

Usage

✅ Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

⚙ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "com.typesafe.sbt", artifactId = "sbt-multi-jvm" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.typesafe.sbt", artifactId = "sbt-multi-jvm" }
}]

^{labels: sbt-plugin-update, early-semver-major, semver-spec-minor, artifact-migrations, commit-count:1}

[raboof]

Not sure what's going on here: it seems between com.typesafe.sbt sbt-multi-jvm 0.4.0 and com.github.sbt sbt-multi-jvm 0.5.0, rm -r cassandra-bundle/target/; sbt clean "cassandraBundle / assembly" no longer works - apparently it tries to write to /cassandra-bundle/target/bundle/pekko/persistence/cassandra/launcher but for some reason that directory is missing. I haven't figured out the interaction between sbt-multi-jvm and sbt-assembly yet.

[raboof]

OK, so we're using sbt-assembly in a pretty questionable way here. While I still don't quite understand how the update of sbt-multi-jvm would cause a change in the behavior of sbt-assembly, I don't think sbt-assembly really promised to do what we ask it to do here.

Perhaps it deserves another look whether/how we want cassandra-launcher to work.

[raboof]

#192