UUIDv7 Method 3 implementation

[denizzzka]

It seems, our UUIDv7 generation system is not suitable for high frequency generation (thousand UUIDs per millisecond) - for this purpose implementation does not fully comply with RFC 9562. Namely, in such cases they insist that instead of a completely random number, monotonic counter or monotonic clock should be used: 6.2. Monotonicity and Counters

Here is my implementation of "Method 3" from RFC 9562.

"Method 3" is pretty cool idea here that time divides the data into +/- identical 1/4 microsecond buckets with random 60-bits tails. This should divide into unique all UUIDs in the world that were generated in that 1/4 microsecond moment.

For accurate time stamps I used StopWatch, which internally uses MonoTime. Is it okay to keep MonoTime running for a very long time? Won't it break after six months of continuous running or something like?

[dlang-bot]

Thanks for your pull request and interest in making D better, @denizzzka! 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 + phobos#10862"