[Google Blockly] Register custom procedure blocks in old labs

[mikeharv]

To support the Sprite Lab migration, we implemented custom versions of the new shareable procedures. When we were ready to migrate Minecraft later, we simply needed to register the blocks. (https://github.com/code-dot-org/code-dot-org/pull/55993/files#diff-972ff80c7f8bd964897bbfa702b7e753dd5e99a06b72a5664a259dd6a6be33a7)

Now we can do the same for Maze, Artist (aka Turtle), and Play Lab (aka Studio) to help prepare them for migration. I tested these changes with a variety of Maze levels and saw the expected improvements, detailed below. I didn't specifically test Artist or Play Lab yet, but registerCustomProcedureBlocks doesn't do anything if we're in the CDO Blockly Wrapper, so there's really no risk with this change.

As a review, here are some ways you can tell that we're using our custom blocks:

• Modal function editor should work
• Call blocks have "edit" buttons if the modal editor is enabled
• Definition blocks have an SVG frame if they're on the primary student workspace
• Definition blocks should not have a "gear" UI in the corner
• Definition blocks never turn gray

Block type	CDO Blockly - baseline	Google Blockly - Staging	Google Blockly - this branch
Call blocks with edit buttons - modal Course 4.16.2
Definition block - modal Course 4.16.2		N/A
Definition block - no modal Course E.14.3
Definition block - no modal - undeletable "stone" blocks Course E.14.4

Links

Jira -https://codedotorg.atlassian.net/browse/CT-558

Follow-up work

Support functions with parameters. :(

PR Checklist:

• Tests provide adequate coverage
• Privacy and Security impacts have been assessed
• 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
• Pull Request is labeled appropriately
• Follow-up work items (including potential tech debt) are tracked and linked