Print module names and timings when running unittests.

[maxhaton]

No description provided.

[dlang-bot]

Thanks for your pull request, @maxhaton!

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#15795"

[maxhaton]

Hijacking CI to see what this affects in the test suite

[maxhaton]

@thewilsonator atila approved, I'm just checking that the test suite has anything to say. Something failed before but could've been flake

[maxhaton]

I think the fail is legit but can't work out what

[maxhaton]

module unittest_assert: FAILED in 73.000000 µs

ah ha

[PetarKirov]

@maxhaton can you add a screenshot to the PR description for future reference? I think users would also appreciate a changelog entry.

[RazvanN7]

@maxhaton have you figured out what is the cause of the testing pipeline failure? This is a cool feature and it would be neat to get this in.

[maxhaton]

@maxhaton have you figured out what is the cause of the testing pipeline failure? This is a cool feature and it would be neat to get this in.

I'm basically fixing the test suite first.

[RazvanN7]

@maxhaton any progress on this?