feat(protocol-designer): bring back deck setup drag & drop

[jerader]

closes AUTH-1276

Overview

This PR brings back drag/drop to deck setup with the same functionality as it had in the pre-redesign. You can only drag top-level labware and can not drag: modules or adapters. When we add stacking capabilities, we will need to refactor it to account for that level of stacking.

Test Plan and Hands on Testing

Test that you can drag and drop any labware to any slot on the deck (minus trash bins/waste chutes). If the labware is not allowed to that slot, you should see the warning blockedSlot label indicating that you can't drop it there.

Changelog

• added LabwareControls, AdapterControls, and SlotControls for the deck map and DeckItemHover is now refactored into OffDeckControls since its used only for off deck. The reason why they needed to each have their own is because the react dnd considerations are different for each
• added DragPreview which is responsible for the lighter container when you are actively dragging something around
• expand RobotCoordinateSpaceWithRef to return getRobotCoordsFromDOMCoords which is used in DragPreview to determine the DOM coordinates
• update DeckSetupDetails to accommodate those new controls
• deleted unused utils that were used for labware<>adapter compatibility, since now, we take the labware def and search for the labware stacking offsets's adapter compatiblity
• added util for getSwapBlocked to be used for labware<>module compatibility
• updated moveLabwareFormErrors to also use the new labware<>adapter compatibility method

Risk assessment

mid- affected deck setup and is the bulk of the 8.4.1 release

[jerader]

@alexjoel42 & @y3rsh - i had to update how we are selecting slots in cypress because this PR adds a lot more complexity to it (basically, hovering of a slot, adapter, and labware each have their own hover component now instead of sharing one). instead of our previous logic that had the slot's exact foreign object x,y location, I added a data-testid with the slot id. The reason why i did this is because due to the various hover components, the foreign object x,y location is sometimes 0,0 but the data-testid stays the same regardless 😄

please take a look at my cypress changes when you have time!

[jerader]

depending on if the hover is on a slot/module or labware/adapter, the copy is different. this was actually always the case so not sure why cypress is mad at it now. Figured a regex to fluctuate between both options was the easiest @alexjoel42 @y3rsh