Event Highlighting: Optimize performance

[thgrund]

I have some strategies to optimize the performance of the event highlighting. It should help mainly to stabilize the editing of big files. The current implementation should be fine for live coding performances.

Here are the points I want to address:

1. Consider the timestamps of the Pre BundleStmap osc bundles. This will ensure, that we do not miss any packages and we can add a latency value.
2. Reset the current state when a hush was received
3. Exclude the calculation to a web worker
4. Replace tokens, when an already set line will be overwritten

For each of these points I would like to create a separate PR. This issue should bundle the communication.

[thgrund]

@ndr-brt as you can see, I changed this PR to Draft: github.com//pull/223

I postpone it, because it makes the code base way more complex. In any case I would like to tackle the other points first and do this web worker stuff later.

[thgrund]

I was able to integrate all the optimization strategies so far and it improves a lot. But I keep it on my fork as long as we need time for reviewing the currently open PRs. I want to resolve them first, before I create more MRs. But I have a clear plan now. For everybody who is already curious and wanna try it out, you can find all the performance optimizations I came up so far here:
https://github.com/thgrund/pulsar-tidalcycles/tree/mrreason-setup-no-worker