[BUG] Java Argument for adding additional mod folders is ignored by the launcher so the mods don´t show up

[NextRaven10]

Please confirm the following.

• [x] I checked the existing issues for duplicate problems
• [x] I have tried resolving the issue using the support portal
• [x] I have ensured my Modrinth App installation is up to date

What version of the Modrinth App are you using?

v0.8.9

What operating systems are you seeing the problem on?

Windows

Describe the bug

When I add the following Java Argument to add additional mod folders they are ignored by the launcher so the mods no longer show up / can be updated even though they are still loaded when the game starts -Dfabric.addMods=mods/libs;mods/performance;mods/customization;mods/content

Steps to reproduce

1. Create a new profile in the Modrinth App
2. Add some mods
3. Create a subdirectory in the mods folder: for example mods/libs
4. Move the mods that you want in that folder for better organization to the mods/libs folder
5. Add the Java Argument -Dfabric.addMods=mods/libs;mods/performance;mods/customization;mods/content which makes it so Fabric checks for the following folders in the mods folder: libs, performance, customization and content
6. See that the launcher no longer shows the mods even though they are still installed and available if you start the game

Expected behavior

That the Launcher would still show the mods if this Java Argument is set and preferably even be able to update them without moving them away from their folders

Additional context

No response