bug: rethink the collision action model

[poneciak57]

Rethink on how actions should be performed.
Idea of giving and extracting payload is fine but not everythink is implemented great currently.

ideas

• state subscription - headhog can subscribe to frog state so when it is changed it can perform some action (be carefull here, poor implementation can lead to "memory leak" where bunch dead headhogs would be still referenced as subsribers)
• enchance collision checking - extend collision action entry to have 3 actions like collision start collision tick collision end it will require better system implementation but can improve on how actions work

Feel free to add your ideas on how we can redesign current system to imadietly notify headhogs on whenever they should start moving and on how we can overally improve this disaster