feat: added min duaration checking in RepositoryConfig

[sriganeshres]

Fixes: #84

I have added a serilazed min_ci_duartion field which takes care that atleast 60 seconds of testing is being done.

[Kobzol]

Hi! This is a good start, but the bot should actually use this value, and check that the CI workflow has not in fact completed in a shorter time than this.

[sriganeshres]

I will check on that. So i think we need to write a test and ensure that min_ci_time is maintained or not right?
Or a new struct which takes every workflows start and end time and then verifes that it is under minum time or over minimum time.

[Kobzol]

Thanks for the PR, it's a good start. Left one comment about the actual logic that should happen on failure.

We should also add some basic tests for this. You can check the existing tests to see how we define them.

[Kobzol]

I left a few more comments. You can find tests e.g. at the bottom of the workflow.rs file.

To run tests locally, you'll need to setup a DB, which I tried to describe in docs/development.md. Let me know if you have any questions about that.

[Kobzol]

Sorry for the long review time, I was (and still am) very busy.

Left a few comments, and we still need tests. If you don't want to work on them, it's fine, I can add them later.

[sriganeshres]

@Kobzol I have made the changes can you review them and can you give me a idea of tests to write regarding this.

[Kobzol]

I implemented a simple test, that also changed internal logic for determining if a check suite was failed or not.

In the future, we should also generalize the workflow status to have explicit information about running for too short, as the error message in this case is confusing. But let's not do that in this PR.

[Kobzol]

It seems like your forcep ush removed my commit, but that doesn't matter, I will add the tests in another PR. Could you please squash the commits? I will merge this PR after that. Thank you!

[Kobzol]

Thank you! :)