Remove CDO Blockly Wrapper and stop importing code-dot-org/blockly

[mikeharv]

Last year, we completed the migration of all student/teacher facing labs to mainline Blockly. However, we were still maintaining both Blockly wrappers due to:

• The flexibility of being able toggle ?blocklyVersion=cdo internal, primarily for gut-checking and regressions
• Unit test reliance on our Blockly fork.

The latter issue has been resolved with:

• use Google Blockly for unit tests #66717

As far as I am aware, we are no longer relying on n the URL parameter, so it feels like the right time to finally take the next big step. This work does the following:

• removes blocklyVersion from controller and disables the URL param
• removes blockly.js script, which would initialize the cdo Blockly Wrapper
• removes cdoBlocklyWrapper.js and directly related util files
• ends the importing of code-dot-org/blockly (and pepjs)

Note that pepjs was used to make Sprite Lab's location picker field work with CDO Blockly. [Slack context from 2021]

Testing story

No test changes are expected here as this whole branch is essentially cleaning up code that is no longer used!

Follow-up work

Rename and being unwinding the Google Blockly Wrapper.

PR Creation Checklist:

• Tests provide adequate coverage
• Privacy impacts have been documented
• Security impacts have been documented
• Code is well-commented
• New features are translatable or updates will not break translations
• Relevant documentation has been added or updated
• User impact is well-understood and desirable
• Follow-up work items (including potential tech debt) are tracked and linked

[github-actions]

🖼️ Storybook Visual Comparison Report

✅ No Storybook eyes differences detected!

[mikeharv]

This file became redundant with the modifications to setupBlocklyGlobal made here: https://github.com/code-dot-org/code-dot-org/pull/66717/files#diff-01014c0cae568cca0fb3270c483ad8f697a04895cbaedcc4c1e4623a50654a9a

[molly-moen]

🎉 🥳 🎉

[ebeastlake]

I have a stupid tangentially related question: use_blockly now references this statement, yeah?

use_blockly = !use_droplet && !use_netsim && !use_weblab && !use_javalab

We don't need to maintain that conditional (for Music Lab, Web Lab 2, etc.) because all of our new labs are being added via Lab2, correct?

[mikeharv]

I didn't touch use_blockly but that sounds plausible to me, but I'd have to confirm. Also Music Lab doesn't use any of the tools listed in that conditional, so I'd expect it to evaluate to true in any case.

[ebeastlake]

One possibly silly question (and maybe we'd want to rename that param in the future, to something like uses_nonlab2_blockly for clarity, depending on the answer), but otherwise, the PR LGTM and what an exciting milestone!