Feature: Package API

[pauliesnug]

No description provided.

[pauliesnug]

@LynithDev generate_contexts explaination:
basically, it collects the file hashes of all the mods/resourcepacks/whatever inside the cluster, and then it associates metadata with them:

1. it is called if a mod file is added manually to the file system
2. it is called regularly on cluster syncing
3. Managed types are based around Modrinth API responses, they should be easily mappable to modrinth, except that i put package in place of project since that is what curseforge uses iirc. (we should rename most references of managed packages into projects to be more aligned with the modrinth api)
4. Mapped types use a system for inferring the ID of each package. each package has PackageMetadata which can map to Managed or Mapped right now, but we should rename Managed to Modrinth and add Curseforge datatypes for eahc provider inside PackageMetadata.
5. i can work on the system for inferring mod metadata based on the mod file right now, or i can work on making your package api/modrinth package api integrated with the Managed (to be renamed Modrinth) package api.