stage2: add an explicit padding field to avoid Valgrind warning

Adds a `unused: u32 = 0` field to `Zir.Header`.

We could leave this as padding, however it triggers a Valgrind warning because
we read and write undefined bytes to the file system. This is harmless, but
it's essentially free to have a zero field here and makes the warning go away,
making it more likely that following Valgrind warnings will be taken seriously.
3d9b6cfcc9Andrew Kelley committed on 8/29/2022, 12:07:21 AMparent56129d2
1 file changedLine totals unavailable