Decouple Playground from SICP Workspace

[RichDom2185]

Description

The tight coupling is blocking a couple planned changes related to refactoring to make use of language configs.

Fixes #2410.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Code quality improvements

How to test

Checklist

• I have tested this code
• I have updated the documentation

[coveralls]

Pull Request Test Coverage Report for Build 5697407953

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 6 of 246 (2.44%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.7%) to 35.39%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/pages/sicp/subcomponents/SicpWorkspace.tsx	4	244	1.64%

Totals
Change from base Build 5696911054:	-0.7%
Covered Lines:	5474
Relevant Lines:	14456

---

💛 - Coveralls

[RichDom2185]

This PR will first require the language config object to be moved from a hardcoded Playground state to be under the workspace context instead. Currently, the SICP Workspace still inherits and affects the state of the Playground, so this should not be merged yet.

[ianyong]

This PR will first require the language config object to be moved from a hardcoded Playground state to be under the workspace context instead. Currently, the SICP Workspace still inherits and affects the state of the Playground, so this should not be merged yet.

The overall direction of this PR looks good. I'll look through the final version of this PR thoroughly since it's mostly checking that the workspaces are separated correctly.