[All] Fix BuildalyzerCracker so it can work on .NET 10

[MangelMaxime]

Fix #4252 for Fable 4

---

BuildAlyzer has a bug with .NET 10, there is a fix available since 1 month
but no sign of a release for now.

For this reason, we want to use a local version of BuildAlyzer with the fix included
and remove our own version later on.

See:
- Buildalyzer/Buildalyzer#318
- Buildalyzer/Buildalyzer#319

To build the custom version of Buildalyzer:

Note for Fable 4, we needed to backport their fixes (I have no idea if I did it correctly
but it seems to works ¯_(ツ)_/¯ )

1. Clone https://github.com/MangelMaxime/Buildalyzer/

2. Checkout branch buildalyzer-5-hotfix-net-10

3. Run dotnet build -c Release && dotnet pack -p:Version=5.0.2-fable-001

4. Copy the *nupkg and *.snupkg to the Fable LocalPackages folder.

   cp /bin//.nupkg /LocalPackages/
   cp /bin//.snupkg /LocalPackages/

[MangelMaxime]

I tested this fix by modifying global.json in this repo, to request .NET 10 and it works.

If someone want to test it before I make a release (probably on Monday as I am not available this week) here are the instructions:

1. Clone this PR

2. Run ./build.sh package

3. This will give you can command to execute to install the local version of Fable for example:

   dotnet tool update fable --version 4.999.0-local-build-20251121-231150 --add-source /home/mmangel/Workspaces/Github/fable-compiler/Fable/fable4-fix-buildalyzer/temp/packages
   

   Run it

4. Run dotnet fable as normal in your project who is using .NET 10

5. It should work now

cc @cr3wdayt5p @halcwb