Make asset extraction a local action

[kralverde]

Description

With changes with minecraft versions, asset files can have massive changes causing a lot of bloat on the git repo that can lead to MBs of extra un-needed data.

This PR introduces a script to generate and move asset files from the extractor to their locations in the project root as well as a workflow artifact for users to download rather than extract if they prefer

Checklist

Things need to be done before this Pull Request can be merged.

• Update workflows to add a compressed archive of extracted files for those who don't want to extract them locally themselves
• Update workflows to extract assets before building
• Add windows scripts
• Add bash scripts
• Code is well-formatted and adheres to project style guidelines: cargo fmt
• Code does not produce any clippy warnings: cargo clippy
• All unit tests pass: cargo test

[DataM0del]

If you want to save space without setting the depth to 1, you'll probably need to use a tool to remove the assets directory entirely from the git history and push that.

[kralverde]

I think this is more a forward looking solution. Re-writing got history is a pain with minimal benefits rn imo

[OfficialKris]

Also, it is no longer just the assets folder. There are extracted JSON object files under pumpkin-world/assets/. The world assets folder is currently 50MiB and that is with just one revision. Any changes would bump that up significantly since the files are one line, minus any git optimizations.

The .git folder on my machine is currently 30MiB which includes many other branches and their revisions. So I don't think current history is too much of a problem.

[OfficialKris]

Is there a reason to use os dependent scripts rather than running a rust program?

[kralverde]

Is there a reason to use os dependent scripts rather than running a rust program?

I suppose not... but I think it's a bit overkill for what boils down to running commands in a sequence