Refactor timer gate and fix goroutine leak problem

[Shaddoll]

What changed?

• Move timer gate interface and implementation to common/clock package
• Rename RemoteTimerGate interface to EventTimerGate
• Change the implementation of localTimerGate:
  • get rid of the goroutine and fix the goroutine leak problem in history queue
  • make it multi goroutine safe
  • make it behave like golang's builtin time.Timer type
• Remove Close method and Introduce Stop method which has a different behavior:
  • The Stop method behaves like the Stop method of time.Timer. It just clears the existing timer if any. A new timer can be reset via Update method.

Why?
Code refactoring and bug fixes

How did you test it?
unit tests

Potential risks

Release notes

Documentation Changes

[taylanisikdemir]

should we change this to avoid blocking?

select {
	case <-t.timer.Chan():
	default:
	}

[Shaddoll]

It's safe to block. As of go 1.23, Stop method always returns true if the timer is not read from the channel, so we don't go to this branch. And before go 1.23, this is the correct way to stop a timer and drain the channel.