fix: dont activate base delete areas for keyboard moves

[maribethb]

The basics

• I validated my changes

The details

Resolves

Fixes #9721

Proposed Changes

• updates the default delete area implementation to not delete things if a keyboard move is in progress
• removes the toolbox's override of wouldDelete since it was not different than the base implementation (please double check me on that)
• updates the toolbox and trashcan various onDragEnter/Exit/etc to not fire if it's a keyboard drag

Reason for Changes

The reason I chose this approach is it updates the default delete area to not trigger for keyboard moves, but allows developers to customize it if they do want their delete areas to trigger for keyboard moves

An alternative was to have the dragger just not fire any of the drag target methods if the drag target was also a delete area. but that was actually more complicated due to various factors (e.g. if you are moving from a regular drag target to a delete area, you have to make sure to trigger the onDragExit for the regular drag target but NOT trigger the onDragEnter for the delete area). And it's less customizable and explainable for developers implementing their own drag targets.

Test Coverage

i will add a test case for this before i merge this but wanted to get review on the approach first because i have another commitment today before i can write the test

Documentation

we don't have any documentation for delete areas but if we did we should tell developers they should probably not activate them for keyboard moves

Additional Information

[maribethb]

added tests