cornerstonejs tools convention: one tool multiple callbacks

[Ouwen]

Current cornerstone tools follow the structure of callbacks which are associated with events. For example,
https://github.com/cornerstonejs/cornerstone3D-beta/blob/2a336d5bd6bb0af865d99ffd8af48ba1ce779f64/packages/tools/src/tools/StackScrollTool.ts#L15-L19

There are currently tool some duplicates for different input types (e.g.)
https://github.com/cornerstonejs/cornerstone3D-beta/blob/2a336d5bd6bb0af865d99ffd8af48ba1ce779f64/packages/tools/src/tools/StackScrollToolMouseWheelTool.ts#L14-L15

This requires users to register two tools:
StackScrollTool for touchDrag and mouseDrag events
StackScrollToolMouseWheelTool for mouseWheel events

Rather than having two separate tools, we can merge the functionality of the mouseWheel callback into the stackScrollTool and provide an API to configure these callbacks on/off without the need to register a separate tool such as the below.

{
   touchDragEnabled: boolean | (evt: EventTypes.MouseDragEventType) => boolean; 
   mouseDragEnabled: boolean | (evt: EventTypes.MouseDragEventType) => boolean; 
   mouseWheelEnabled: boolean | (evt: EventTypes.MouseDragEventType) => boolean
}
   

Same convention can be applied to v3 Pan / MultiTouchPan, StackScroll MultiTouch, Zoom / Zoom pinch / Zoom wheel.