mods(Safe I/O): Only allow creating files with whitelisted filetypes

[GeckoEidechse]

Only allow creating files with whitelisted filetypes to prevent writing .bat or .vb files with Safe I/O that could then be called using some exploit (e.g. #674), we should prevent writing file types that by default are interpreted as executable.

Whitelisting was chosen over blacklisting as we can always extend the list and don't have to worry about potentially forgetting to blacklist a certain filetype.

Of course this doesn't prevent writing a bash script to a .txt file and then somehow getting Windows to interpret it as a batch file.

Reading files is not restricted to filetypes as we are primarily concerned with creating files here.

Supersedes #675

Completely untested atm.

Testing instructions:

1. Use the following mod: GeckoEidechse.Safe-IO-Testing.zip
2. Go into private match and start a match
3. Enable cheats (sv_cheats 1)
4. Open console and run

   script GeckoSaveFile()
   

5. Go to <profile folder>\save_data\GeckoEidechse.Safe-IO-Testing\
6. Check that only test1.txt exists but no test2.bat or test3.

[GeckoEidechse]

I wrote this on a system that is unable to compile Northstar and without having written C++ for like more than half a year, would be surprised if it even compiles xD

[Alystrasz]

@ASpoonPlaysGames is also working on that (#675), are you aware of that? 😄

[ASpoonPlaysGames]

@ASpoonPlaysGames is also working on that (#675), are you aware of that? 😄

ngl that PR is kinda dead, i've just not had the time to do much lately. Honestly this PR might be preferable to mine.

[Alystrasz]

@GeckoEidechse you created the branch on the main repo so we cannot update it 😢

[barnabwhy]

This isn't directly related to the PR but I noticed while reviewing that the code immediately below directly locks and unlocks the mutex, but ideally it should be using std::lock_guard at the start of the try catch block so that we don't need to explcitly unlock on every scope exit.

[RoyalBlue1]

Code looks good I didn't test though.
If we plan on staying C++20 using !whitelist.contains(extention) might be more readable than whitelist.find(extention) == whitelist.end() but that is up to preference and shouldn't be blocking really

[GeckoEidechse]

mfw when 3 people reviewed the PR and no one noticed that the return statements are missing in the check :clueless:

[Alystrasz]

Code looks good, test mod works as expected: