Add matchers to Klock.

[dragneelfps]

Related to #1156.

[dragneelfps]

@sksamuel I have created this draft. I wanted to get an opinion on the approach I have used. Also, what are the matchers that should be implemented.

[LeoColman]

I believe you're on the right track.
I recommend adding some matchers for numbers, like Time.shouldHaveMinutes(5) or something similar.

I'm not sure if you're using our current datetime matchers as inspiration, but that can be a good starting point if you feel lost! I believe you are doing things that way already tho

Take a look

[dragneelfps]

@Kerooker I think I have added all the required matchers. I haven't documented the matchers like done in existing code since, I didnt find any need for doing it, as its self documenting. But if you want me to add docs, then I can.
I have added some tests as well.
I dont know if publishing works on that. Need to check on that.
Other than that, I think the PR is ready to be reviewed.

[sksamuel]

If you can address the feedback @dragneelfps I will merge. This will be an excellent addition.

[dragneelfps]

@sksamuel feedback taken and code changes done.

[dragneelfps]

Build failing with:

* Where:
Build file '/home/runner/work/kotest/kotest/kotest-assertions/kotest-assertions-klock/build.gradle.kts' line: 70

* What went wrong:
Could not read script '/home/runner/work/kotest/kotest/publish.gradle' as it does not exist.

Any help?

[sksamuel]

The build was changed over the weekend so publish.gradle doesn't exist. That's ok, we can merge.