Tech Debt: implement unidirectional data-flow for text-node service

[bensivo]

In the current implementation of the text-node service, the service manages events, state, and rendering all in one jumbled mess.

For long-term maintainability, we need to refactor this service so it follows an easier-to-understand pattern of:

1. Receive event
2. Update state
3. Update UI