Upgrade dependencies to move away from repo.scala-sbt.org

[mkurz]

I started to block repo.scala-sbt.org and repo.typesafe.com in my /etc/hosts.

• sbt-paradox 0.10.3 (up to 0.10.5) still hosted on repo.scala-sbt.org, migrated to maven central with latest 0.10.6
• sbt-dynver 4.1.1 still hosted on repo.scala-sbt.org, latest version on maven central however.

This pull request depends:

• Upgrade dependencies to move away from repo.scala-sbt.org lightbend/sbt-paradox-apidoc#271
  EDIT: https://github.com/lightbend/sbt-paradox-apidoc/releases/tag/v1.1.0
• Upgrade dependencies to move away from repo.scala-sbt.org lightbend/sbt-paradox-project-info#40
  EDIT: https://github.com/lightbend/sbt-paradox-project-info/releases/tag/v3.0.1

TODO:

• Upgrade sbt-paradox-material-theme (needs to move under com.github.sbt and a new release).
• cut new pekko-sbt-paradox release
• Upgrade in Upgrade dependencies to move away from repo.scala-sbt.org pekko-http#453 and Update sbt-paradox to 0.10.6 pekko#1061, so in build.sbt we don't need the three force() dependencies anymore, but instead nail down parboiled to v1.4.0.
• Also in incubator-pekko-connectors can be done the same, also (Update sbt-site to 1.5.0 pekko-connectors#362) needs to be upgraded

After merging this can you cut a 1.0.1 release? Thanks!

[mkurz]

Hmm actually pekko itself could also then upgrade
sbt-paradox-apidoc
sbt-paradox-project-info
to latest version as well...
https://github.com/apache/incubator-pekko/blob/f6da401abf69e7f45d9705fcf611a5d6726c5bc3/project/plugins.sbt#L40-L41

[pjfanning]

We're using older versions to keep java 8 compat. It may be time to abandon that.

[mkurz]

+100 to drop support for Java 8. The world is moving on, even Akka:

• https://doc.akka.io/docs/akka-http/10.4/migration-guide/migration-guide-10.6.x.html#support-for-java-8-removed
• https://doc.akka.io/docs/akka/2.9/project/migration-guide-2.8.x-2.9.x.html#support-for-java-8-removed

Play 2.9/3.0 also dropped Java 8, and we will even drop Java 11 in our next major release.
Keeping Java 8 (and even 11) is getting more and more of a pain, since quite some dependencies started a while back ago already to not publish Java 8 compatible artifacts anymore.

[mdedetrich]

@mkurz Closing this PR since its invalid, has been solved with #92 and #97