Remove workspace drag surface and block drag surface

[BeksOmega]

Describe the bug

With the drag surface (~2-5 FPS) on b92cbd3:

Without the drag surface (~10 FPS) b92cbd3:

To Reproduce

Steps to reproduce the behavior:

1. Go to the playground.
2. Hit the 'Airstrike' button
3. Go to the performance tab of the chrome devtools.
4. Enable recording screenshots.
5. Set CPU Throttling to 6x.
6. Start a recording.
7. Drag the workspace left... right... and left again.
8. Stop the recording.

Expected behavior

Ideally we wouldn't drop frames while dragging. Unfortunately most of the costs of dragging occur in the SVG engine, which we don't have a ton of control over.

Additional context

I have been able to make this a lot faster by changing things from using setAttribute to using <element>.style. This lets the browser use its CSS optimizations.

On https://github.com/BeksOmega/blockly/tree/perf/ws-drag (~30 FPS):

But that branch needs a lot of cleanup. Eg this does not work in IE, because IE does not support CSS transforms on SVG elements. So we need some utils that will handle setting SVG locations in a generalized way.

[BeksOmega]

I'm going to reopen this because the removal was reverted due to it being a breaking change, but we still want to remove it in the future.

Note: we're not going to add deprecation warnings b/c we use the surfaces in core, and spamming developers with warnings they can't turn off is not nice.

[rachel-fenichel]

We decided not to include this change in the March 2023 release because it's a breaking change. Instead we're holding it until we release v10.

When reapplying the fix in #6758, also apply #6874 to resolve #6852.

[maribethb]

Note: We need to fix the scroll-options plugin when we release this as well.

[BeksOmega]

Related to: google/blockly-samples#1664