Graphics behaviors are using traditional class/oop approach -> Research switching to simple tables + redux approach

[tredfern]

The animator, sprite, and animation classes are all using a traditional method attached to table approach.
This works well for setting things up and getting code going, but it results in data munged with functions.

Research splitting this into a redux/action based approach. Animations are going to have to be driven by
actions anyway to work within the context of the game. So should everything?