Streamline and rework animation system

[bcthund]

The loaded animations should be static, while the animation system can be added as an instance to any system that needs to have animations. Use templates to differentiate between 2D and 3D usage with a custom Animation type such as t_Animation2D and t_Animation3D with properties that match that instance.

The new system should use a Hashmap stack and instead of doing an update as part of a global draw routine, there should be an update method that can be called at the animation owners discretion.

Animations should be pushed to the stack using a name in a hash map where the name defines the owner of the object. This allows the owner to always access the item regardless of other objects getting added/removed (unlike a VectorMap).

[bcthund]

• [x] Create base animation class to be used as global source for loaded animations
  • [x] VectorMap of loaded animations
  • [x] Init() method, update existing method
  • [x] Load() method, update existing method
  • [x] Calc() method, update existing method
  • [x] get() method, create to get an animation by image name or ID
  • [x] add operator[] overload as simple version of get()
  • [x] Create a t_AnimationItem2D
  • [x] Create a t_AnimationItem3D