Comment out subgraph copy_data() callback for now - nothing happens here
Fleshing out/modifying logic for how bone nodes work

For now, bones are only represented as operation nodes used to represent
the evaluation steps for evaluating their transforms. This should help
keep the total number of nodes down, and prevent us from having to
have components within components for now (since there's not much more
that can exist for each bone)
Added bone component struct
OpNode constant define for pose-eval operation
Fixed Bone Operation Node Logic + Added Pose Operation Node
Skeleton for Bone Component Node
Use standard component logic for bone component
Logic for adding/removing bone component from pose component
WIP changes to find bone component from pose component

TODO: we now have a problem locating specific bone operations from
      bone, as they all have same name!