Allow specifying alternative resource- and datapack download directories

[DaXcess]

Please confirm the following.

• I checked the existing issues for duplicate feature requests
• I have checked that this feature request is not on our roadmap

What parts of Modrinth is your feature request related too?

Modrinth Desktop App

Is your suggested feature related to a problem? Please describe.

roadmap leads to 404 by the way

Some modpacks have required resource- and/or datapacks. These modpacks often use mods like Simple Resource Loader (or similar alternatives) to allow for specifying required (and optional) data- and resourcepacks, making it easier to select these during world creation for example (not having to move files to some temp directory from the datapacks directory).

These mods usually do not check the existing resourcepacks and datapacks directory (in fact I don't think datapacks is even a "standard" directory, and only used by modrinth to track installed datapacks).

This makes modpack authors usually put these files in the directories that these resource loader mods expect them to be (for example: resources/datapack/required). These directories aren't tracked by modrinth (and it looks like there is no option to do so), causing the exported .mrpack file to be bloated in size (as the files are bundled directly), and the data- and resourcepacks don't get attribution when installing the modpack.

Describe the solution you'd like

A way to allow users/modpack authors to specify additional directories for modrinth to scan resourcepacks/datapacks/shaders would fix this problem. An example could be in the pack settings, add a "additional resources" menu where you can specify directories in the pack that should be scanned for additional content.

Describe alternatives you've considered

Something that has worked locally for me and friends was modifying the modrinth.index.json file, and changing the path property from datapacks/some_random_datapack.zip to resources/datapack/required/some_random_datapack.zip (in the case of Simple Resource Loader).

This works fine and all but is not a great user experience, but it does mean that the app already supports such a feature. I'm also not sure if such changes would cause a modpack to be rejected were they to be uploaded to modrinth (I've only used exported modpacks with this technique so far, never uploaded one).

Additional context

No response