Add zig logo the the compiler binary on Windows

[LucasSantos91]

On Windows, an image can be embedded into an executable and displayed by the operating system. This PR adds the zig logo to the zig binary. This gives Zig a more polished look.
This is how it looks in light and dark mode:

The logo was taken from here. The source svg file was transformed into a .ico file via svg2ico.com.
The .ico file is an archive. It contains 4 renditions of the logo as PNG files, for different sizes: 16x16 pixels, 32x32, 48x48 and 256x256, which are the sizes recommended by microsoft.

[squeek502]

I thought about doing this sort of thing as well when first adding support for Windows resources 🙃.

The CI failure is due to zig2 disabling support for win32 resources (and all JIT commands). The easy solution would be to only add the resource file when compiling a stage4 compiler, but unsure how to go about that at the moment.

[alexrp]

This should probably come with a *.ico binary entry in .gitattributes?

[alexrp]

Nit: Missing a trailing newline.

[LucasSantos91]

I still haven't figured out a way to know which stage we are currently executing, in order to skip the addWin32Resource call in stage 2. This is harder than it looks.

[Rexicon226]

The zig_backend is the same, you want to check the dev environment if rc is included.

[squeek502]

Unless I'm thinking about it wrong, it's the dev environment of the zig binary that's being used to compile that's relevant, which can't currently be queried by build.zig I don't think.

I guess you could spawn <current zig binary> rc /? and see if it fails or something like that, but seems like something better should be possible (and due to the JIT compilation of the rc subcommand, that way of querying the capability could take a while).

EDIT: Spawning <current zig binary> --help or <current zig binary> version would be a way of querying it. Those fail with zig2

[Rexicon226]

Ah, I misunderstood the issue.
Then what about adding a @import("builtin") flag for checking whether rc was included?

[LucasSantos91]

Well, messing with builtin would be more intrusive than I was expecting for this PR.
Having to rely on something failing would also be more complex than this feature should be.
Perhaps importing builtin and checking if the zig_backend field is greater than 11. Apparently all stage 2 backends are between 1 and 11.

[Rexicon226]

When would the value be greater than 11?
Anyways, I think the best solution here is to just add an option for including the logo and disabling it in the CI or maybe only include it for the stage4 build.

EDIT: actually that wouldn't work obviously, since we byte-compare stage3 and stage4. Do we really need to test adding it in CI?
EDIT2: do we byte-compare on windows CI?

[LucasSantos91]

When would the value be greater than 11?

Yeah... the documentation doesn't say. There are no enums for stage3 or 4, I just assumed these stages would set a different value...

[Rexicon226]

They do not, since the zig backend remains the same.

[LucasSantos91]

I don't think this is possible. Stages 3 and 4 need to be identical. Stage 3 is compiled from stage 2. Stage 2 doesn't support resources.
Not a huge deal, just a bit sad. It looked neat.

[marler8997]

If/when someone makes another attempt at this, let's try to avoid unnecessary antialiasing along "orthogonally aligned boundaries". In general this can't or at least is very hard to do automatically from and SVG, you might need to do some fixes by hand after such a conversion.