sloth: bump to 0.1.0-M2 & patch loose class files at -cp

[Gedochao]

This makes Sloth patch loose classfiles passed via -cp.
It also bumps Sloth to 0.1.0-M2: https://github.com/VirtusLab/sloth/releases/tag/v0.1.0-M2

Behaviour without this change

Given a lazy.scala file:

lazy val hah = true
def slothful: Boolean = hah

when

scala-cli compile --server=false lazy.scala -S lts --jvm 8 -d cp
scala-cli run --server=false -e 'println(slothful)' -cp cp --sloth --power --jvm 25  

we still get the warning

WARNING: A terminally deprecated method in sun.misc.Unsafe has been called
WARNING: sun.misc.Unsafe::objectFieldOffset has been called by scala.runtime.LazyVals$ 
(file:(...)/scala-library-3.8.4.jar)
WARNING: Please consider reporting this to the maintainers of class scala.runtime.LazyVals$
WARNING: sun.misc.Unsafe::objectFieldOffset will be removed in a future release

Checklist

• tested the solution locally and it works
• ran the code formatter (scala-cli fmt .)
• ran scalafix (./mill -i __.fix)

How much have your relied on LLM-based tools in this contribution?

extensively

How was the solution tested?

included automated tests

[Gedochao]

The native image failures seem to be caused by a bug in Sloth's JarProcessor.
They're not directly related to the fix here, but seem to have been activated by the changes.
While we could theoretically work around it here, I'm thinking it's actually best to fix it upstream first:

• ClassLoaderClassWriter silently falls back to Object; JarProcessor should accept a caller-provided resolver sloth#1

Moving this PR to draft for now.

[warcholjakub]

Things I noticed before the PR got drafted

[Gedochao]

Upstream fix:

• Let callers supply the class hierarchy when patching a JAR  sloth#2