feat!: Use custom EventEmitter implementation

[Im-Beast]

BREAKING CHANGE Will break most of the code regarding events

Plans:

• No need to create custom events
• Allows easy disposal of listeners
• No need to destructurize object to get needed data
• Better RAM (maybe CPU too) utilization
• Overall improvement in Developer Experience.

Progress:

• [x] Remove EventListener's when component is removed
• [x] Add possibility to tie EventListener directly to a component
• [x] Make Tui.run() start application but not return async generator
  • Same with Tui.update() and Tui.render()
  • Add Tui.remove() that would destroy Tui and stop it
  • Add Tui.dispatch() which will mimic how Tui gets closed currently (automatically via CTRL+C etc.)
  • EventEmitter will allow to intercept incoming data when needed

[Im-Beast]

Notes:

• Maximal framerates might appear smaller but it was apparently caused by using CombinedAsyncIterator, however now frametimes are way more consistent.
• Previously when updateRate was set to lets say 1000 / 144 (144FPS) then it often overshoot and caused rendering ~160-180FPS, now it's no longer an issue.
• Changing size of the Tui caused by resizing terminal is now smooth as butter
• CPU usage seems about the same (maybe slightly lower) but previously it could spike a bit high, this no longer happens (needs testing)
• Memory usage is about the same (needs testing)
• Tui is now way more stable when it's time to unload it (in watch) and on closing
  • There were cases where it could still run in the background after closing, no longer the case
• Tui's close event has been renamed to dispatch