Remove @code-dot-org/bramble package, load bramble from S3 package

[maddiedierker]

This removes our @code-dot-org/bramble NPM package dependency. As far as I can tell, it was only used for loading require.min.js when loading WebLab:

code-dot-org/dashboard/app/views/weblab_host/index.html.haml

Line 10 in 9bf9e58

%script{src: "/blockly/js/bramble/thirdparty/require.min.js", 'data-main': webpack_asset_path('js/brambleHost.js')}

However, we point to the S3 build when we instantiate Bramble:

code-dot-org/apps/src/weblab/brambleHost.js

Lines 599 to 600 in 9bf9e58

	url:
	'//downloads.computinginthecore.org/bramble_0.1.26/index.html?disableExtensions=bramble-move-file',

This means WebLab actually uses the S3 build, not the NPM package, so I have removed the NPM package. I will need to do some follow-up work to indicate this in code-dot-org/bramble (there are currently no Code.org-specific instructions around how to publish/consume a new version of Bramble, so I've added them here).

These changes were previously part of #36710 (general "upgrade Bramble" PR), but I realized that this change can and should ship on its own to make sure there are no regressions prior to upgrading.

I also did some clean-up around "dev mode" because you had to comment/un-comment like 4 different things in different spots before. Now, if you set @dev_mode to true in WeblabHostController, everything will point to your local Bramble server.

Links

• STAR-1261, which encapsulates shipping the Bramble upgrade.

Testing story

Relies on existing UI tests, which make sure that Bramble loads properly.

Reviewer 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