[Bug]: WeekBox forces mods to become executables when the `.git` folder is present

[KirbyKid256]

What happened?

I'm trying to make a symbolic link of a few mods I've been working on and put it in the list of mods I have installed. But for the mods with a .git folder (which is required for GitHub), it automatically sets it to an executable. These are, however, NOT executables, but Codename Engine modpacks.

Steps to reproduce

For this example, I'll be using the Sunday Night Plumbin' repository.

1. Clone mod somewhere in your file system.
2. Add that newly cloned directory to WeekBox with "Add local mod"
3. Complete the steps to adding the mod.

It is now an executable. The reason I know that it's the .git folder causing this issue is because it got fixed once I removed it. Even though that is necessary to keep for GitHub.

1. Open installedmods.json.
2. Find the section with the local Sunday Night Plumbin' stuff.
3. Change engineId to codename.
4. BEFORE opening WeekBox, go back into the cloned repository and delete the .git folder

Now it should work. And it automatically sets it back to an executable when you restore that folder.

Environment

• WeekBox version: 2.1.16
• Operating system: Windows
• Install type: Local
• Engine or mod name/version: Codename Engine and Sunday Night Plumbin' public GitHub Repository
• Download source, if relevant: https://github.com/[DeadlyneCode/Sunday-Night-Plumbin](https://github.com/DeadlyneCode/Sunday-Night-Plumbin)
• Progress/status where it failed, if relevant: n/a

Screenshots

Checklist

• I searched existing issues.
• I can reproduce this on the latest version.
• I included the steps needed to reproduce it.