Fix: Use stable release tag instead of moving master branch

Problem

The package was downloading master.tar.gz from GitHub with a hardcoded SHA256
hash. Since master is a moving branch, the hash becomes invalid whenever the
remote repository is updated, causing hash validation failures in CI environments.

This is a fundamental design flaw: hardcoding a hash for a moving target defeats
the purpose of hash validation, which is to ensure artifact immutability.

Solution

Switch to using a specific release tag (3.110.1) instead of the master branch:

• Release tag 3.110.1 is immutable and contains all supported Minecraft versions
  (1.20.6, 1.21.6)
• Hash is tied to a specific, stable artifact that will never change
• Hash validation now works reliably in CI and local environments
• Future releases can be updated by changing the tag and hash

Changes

• Updated base_url to point to refs/tags/ instead of archive/
• Changed download from master.tar.gz to 3.110.1.tar.gz
• Updated hash to
  375a1c0267f395d0a04c01873ca9bae70e23e6bc32b9057d2893ce0a77d86a4a
• Updated extract paths to reflect the new release name

Testing

Verified that data loads correctly for both supported versions (1.20.6 and
1.21.6).