Update async-profiler to v3.0

[SirYwell]

In essence, this PR updates async-profiler to the recently version 3.0.

One main change is that we now don't pull the API from jitpack anymore, but from maven central using the official coordinates (hard to find tbh, but see async-profiler/async-profiler#93 (comment)).

Notable changes:

• This dependency already contains the .so files, so we don't need to include them manually anymore. However, the path changed, but I guess that's fine.
• For amd64, glibc and musl are now supported with one file (since 3.0).
• JfrReader was outdated/not able to parse new profiles anymore. I copied the current changes, only keeping the changes with a // spark comment

There are a few things that could be considered following this PR:

• v3.0 got a replacement for AGCT (see AsyncGetCallTrace replacement async-profiler/async-profiler#795). From my understanding, this isn't the default. It might make sense to use async-profiler with that option
• It might be worth to consider using -e ctimer as it doesn't require perf_events (Accurate CPU sampling without perf_events async-profiler/async-profiler#855)

I tested the changes on linux amd64 and linux arm64.

[lucko]

Happy to merge this, but I think I will wait for v3.1 to drop as there are some commits / bug fixes that have been made since the 3.0 release which I think would be good to have.

[lucko]

Test builds

These are using the latest nightly build from async-profiler (currently 6bd9dfa) - https://github.com/async-profiler/async-profiler/releases/tag/nightly

spark-1.10.113-bukkit.jar.zip
spark-1.10.113-bungeecord.jar.zip
spark-1.10.113-fabric.jar.zip
spark-1.10.113-forge.jar.zip
spark-1.10.113-neoforge.jar.zip
spark-1.10.113-velocity.jar.zip
spark-1.10.113-sponge.jar.zip

Especially interested to hear feedback from anyone using "special" installations, e.g. musl Linux (usually in Alpine docker containers) or OpenJ9 JVMs.

[Teslicek]

spark-1.10.113-bukkit.jar.zip
Especially interested to hear feedback from anyone using "special" installations, e.g. musl Linux (usually in Alpine docker containers) or OpenJ9 JVMs.

Tested with Java Oracle GraalVM 23 in a pterodactyl container using Debian 12.
Minecraft server version was 1.21.1.

No crashes or issues during local testing. Will proceed to upload it to the production server and see what happens.

[flerouwu]

The test builds appear to be working as intended for Velocity and a Paper 1.21.1 server with GraalVM Java 23.

The servers are running as Pterodactyl servers using images found at https://github.com/ProtobitMC/pterodactyl-graalvm.

Thanks for working on a fix!

[Teslicek]

Been running this on the production server for a few days now, no issues, would consider stable.

[rafi67000]

I tested it with GraalVM23, custom paper fork 1.8.9 and everything works fine.
Ubuntu 22.04 aarch64 (Debian 12 container)