Update scalameta to 4.9.9

[scala-center-steward]

About this PR

📦 Updates org.scalameta:scalameta from 4.9.3 to 4.9.9

📜 GitHub Release Notes - Version Diff

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 = "org.scalameta", artifactId = "scalameta" } ]

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

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta", artifactId = "scalameta" }
}]

^{labels: library-update, early-semver-patch, semver-spec-patch, version-scheme:semver-spec, commit-count:1}

[bjaglin]

Previously breaking since 4.9.4

• [4.9.4+] semanticdb-scalac fails compilation  scalameta/scalameta#3738 (4.9.8)

Improvements

• ScalametaParser: keep pos if dropping outer block scalameta/scalameta#3695 (4.9.4)
• Token: define Shebang token, detect and parse it scalameta/scalameta#3812 (4.9.8)

Changes breaking for implementation (but not passed onto the Scalafix API clients)

• Distribute various semanticdb files to own modules scalameta/scalameta#3747 (4.9.8)
• Input/Position: organize implicits, add cross-map scalameta/scalameta#3826 (4.9.9)

Breaking changes (passed onto the Scalafix API clients)

• ScalametaTokenizer: group sequences of whitespace scalameta/scalameta#3786 (4.9.8)

[bjaglin]

Following scalameta/scalameta#3747, this was added to continue building against internal.{symtab,metap} (now directly via semanticdb-scalac-core) & protobuf stubs in internal.semanticdb (now transitively via semanticb-shared). Unfortunately, this brings way too much stuff: `scala.meta.interactive, other unused (internal) classes, and the Scala2 compiler itself.

If this turns out to be a problem, we could either (1) revisit this upstream, or (2) rely on semanticdb-shared and shade only packages we need from semanticdb-scalac-core.

[tgodzik]

The biggest problem here I guess is that we are using internal packages, we should move them out of internal if they are intended to be binary compat or as you suggest shade them in scalafix 🤔

[bjaglin]

Indeed, I will go for (2). For the record: I'll wait for the next scalameta release I guess (since I am effectively blocked by scalameta/scalameta#3786 (comment)), where semanticdb-shared will be cross-built with binary version only.

[bjaglin]

it was not that easy in the end :( #2048