Improve Debug features

• This might be needed in the bitmap log, too, but the tracker pointer isn't intuitive, it's not clear whether the item needs to be highlighted when the tracker tool is selected, or whether then next object clicked will be tracked (it's the latter). Recommendations:
  • Whenever the debugger awaits a single object is to be selected, it should highlight the object directly under the mouse, so they know which object will be selected. Same for when they drag to select, though maybe that feature should be disabled in single object select mode.
  • If objects are already selected when a single object selection tool is active, the selection bound should be either hidden, or - better yet - change color/alpha. I don't want to wipe the previous selection when electing a single object
  • Make these buttons highlight differently than other tools (like the pointer) to illustrate that they are "temporarily active until selection"
• The transform tool seems to select an arbitrary single object in the current selection, this feels odd. Maybe it should transform them all?
• Changing values in tracker windows should try to resolve to the original type, and perhaps ignore and/or warn on invalid entries. Recommendations:
  • Set up tracker field types for primitive haxe types and common flixel types. Each type controls how they are displayed, how they are edited, and how/whether edited values affect the target field. Advanced idea: Allow tracker profiles to define different "styles" for fields of the same type, I.E.: sprite.alpha can be a 0-1 slider where x is a unbounded
• Add FlxG.bitmapLog.remove with overloads that take an id, bitmap or graphic

Start by locating the debugger's tracker and transform tools, the tracker windows, and FlxG.bitmapLog. Review how object selection, value editing, and bitmap-log entries currently work. Done means the listed selection feedback, transform behavior, typed tracker editing, and FlxG.bitmapLog.remove overloads are addressed.