Replace TimeDateStamp with deterministic hash for reproducible builds

[abulgit]

fixes: #21095
I replaced the time-based TimeDateStamp in mscoffobj.d files with a deterministic hash derived from the object file's content.
Implemented a deterministic hash generation system using Blake3.
Used the first 4 bytes of the resulting hash as the TimeDateStamp value.

For Testing -
I compiled the same code at different times, and the object file was the same hash.

abulk@MSI MINGW64 ~/OneDrive/Desktop/hash
$ certutil -hashfile prog1.obj SHA256
SHA256 hash of prog1.obj:
9319df865f216e72e0f63407cae7e00ed08ae00e7b8a486ab34780a60020ec9a
CertUtil: -hashfile command completed successfully.

abulk@MSI MINGW64 ~/OneDrive/Desktop/hash
$ certutil -hashfile prog2.obj SHA256
SHA256 hash of prog2.obj:
9319df865f216e72e0f63407cae7e00ed08ae00e7b8a486ab34780a60020ec9a
CertUtil: -hashfile command completed successfully.

[dkorpel]

Nice work!

[dlang-bot]

Thanks for your pull request and interest in making D better, @abulgit! We are looking forward to reviewing it, and you should be hearing from a maintainer soon.
Please verify that your PR follows this checklist:

• My PR is fully covered with tests (you can see the coverage diff by visiting the details link of the codecov check)
• My PR is as minimal as possible (smaller, focused PRs are easier to review than big ones)
• I have provided a detailed rationale explaining my changes
• New or modified functions have Ddoc comments (with Params: and Returns:)

Please see CONTRIBUTING.md for more information.

---

If you have addressed all reviews or aren't sure how to proceed, don't hesitate to ping us with a simple comment.

Bugzilla references

Your PR doesn't reference any Bugzilla issue.

If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog.

Testing this PR locally

If you don't have a local development environment setup, you can use Digger to test this PR:

dub run digger -- build "master + dmd#21191"