Prevented localized elements from being imported into non-localized regional partner playbook

[jmkulwik]

Short Description: The regional partner playbook is unable to load if any localized elements are required in its dependencies. playbook.js imports the redux store. When the 'projects' reducer (which has an un-needed dependency on a localized element) was added to the redux store, it caused the regional partner playbook to fail to load. This PR removes those localized elements.

Long Description: This is a fix for a bug caused by this PR: #33593
Specifically, the addition of the "projects" reducers to the redux store:

code-dot-org/apps/src/code-studio/redux.js

Line 30 in 094f1d2

projects,

The "projects" reducers imported from a constants file that used localized elements. This caused problems downstream in a page that explicitly does not import localized elements, https://code.org/educate/regional-partner/playbook

Having these localized elements caused the Regional Partner Virtual Playbook to fail to load due to a JS error.

Removing these localized elements from the constants file fixes this issue.

Links

• slack thread

Testing story

Reviewer Checklist:

• Tests provide adequate coverage
• 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

[islemaster]

👍 Looks good!

This looks like a really sharp edge. Let's do some brainstorming tomorrow on how we can prevent similar issues in the future.

[Hamms]

I'd be down to be a part of that brainstorming; this sharp edge appears to be caused by our i18n engine, after all.