build(deps): Update scala-debug-adapter from 3.0.5 to 3.0.9

[scala-center-steward]

Updates ch.epfl.scala:scala-debug-adapter from 3.0.5 to 3.0.9.
GitHub Release Notes - Version Diff

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!

Files still referring to the old version number

The following files still refer to the old version number (3.0.5).
You might want to review and update them manually.

integrations/sbt-bloop/src/sbt-test/sbt-bloop/cross-compile-test-configurations/build.sbt
notes/v1.5.5.md
website/yarn.lock

Adjust future updates

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

updates.ignore = [ { groupId = "ch.epfl.scala", artifactId = "scala-debug-adapter" } ]

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

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "ch.epfl.scala", artifactId = "scala-debug-adapter" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, old-version-remains, commit-count:1

[adpi2]

Found out that the first test in DebugProtocolSpec fails systematically because configuring the debug context takes more than 30s. This only happens on JDK 11, on Ubuntu or Windows. It does not happen on any other JDK, nor on Mac. Configuring the debug context a second time is much faster:

[Debugger][Info]Configured debugger context in 50 seconds
Wed Mar 29 09:57:57 UTC 2023 server started
Wed Mar 29 09:57:57 UTC 2023 server listening on tcp://0.0.0.0:37597
[Debugger][Info]Configured debugger context in 1 second

Could it be that there is a starvation of threads on the first run only? Could it be that we need to warm up some class loader?

As I was not able to reproduce this error locally, I am going to add more logs in the debugger to understand what's happening.