Add "cooldown" period to multiphase trigger

[katspa-sc]

It is currently possible to doubletap space when starting the timer or attempting to time a phase while using multiphase. This can result in a situation, where immediately after the timer has been started a phase is being recorded when using the multiphase feature, eg.

This can be troublesome when using any kind of multiphase amount and results in the user either:

• having to start another solve to get 1 more phase and then having to add the times together
• abandon the attempt

I propose for a toggle setting to be added which would allow the user to have a "cooldown" or grace period after the last phase or timer start has been recorded, during which another phase could not be timed/recorded. This would result in double tapping space or pressing space + letter key at once to not result in 2 phases being recorded in nearly the exact same time.

Since the grace period would be a toggle setting and aimed at helping with the user's hardware issues (like jitter click, faulty key switch etc.) a period of 1s should be more than sufficient, however it would be nice to either be able to choose the grace period from a couple options, or just put in a custom positive integer for milliseconds or full seconds.

[katspa-sc]

Any chance of this being implemented?

[cs0x7f]

Now there's a 200ms cool down after https://github.com/cs0x7f/cstimer/commit/683a043dd87a9ccd46534114e9631e7302864117