Explain rsrc.syso files in README.md

[GG3Hahn]

Questions

• Did you test your changes or double-check that they work?
• Did you read and follow the Atlas Contribution Guidelines?

Describe your pull request

This branch adds a brief section at the end of the README to explain the origin and relevance of the rsrc.syso files in this repo.
The explanation is taken from Zusier's reply on #15.

[Ast3risk-ops]

Is this really something that's imperative for people to know?

edit: if yes, this could use a cleanup, it is way too verbose.

[GG3Hahn]

It's not imperative to know for the general user, and it's (probably) not even imperative to know for programmers.
It is imperative to know when auditing this repo.

For context: I was taking a look at this because the multichoice.exe that I got with the AtlasOS playbook (v0.5.0-hotfix) was flagged by 4 (iirc) antivirus vendors on VirusTotal. So when I looked at it in this repo, I was immediately suspicious of some "random" binary in-between the source files. I was only able to confirm that they are harmless using a hex editor and asking in an issue, therefore I believe it makes sense to explain them in the repo directly.

I'll shorten it a bit if you think it's too verbose.

(Sorry for taking a while to respond)

[pencilnav]

lgtm

[GG3Hahn]

I don't know if you're still looking for less-verbose phrasing since this got un-drafted and approved already. My slightly briefer rendition would look like this:

gameutil/ and multichoice/ both contain a binary file rsrc.syso that gets linked into the executable upon building. They were created with rsrc and contain a manifest required for the GUI module Walk to function. The manifests in question have the exact XML content from Walk's example.

Lmk if you want it pushed.

[pencilnav]

@GG3Hahn the new one does looks better👍 feel free to push it and I'll approve