Refine project share filtering of user inputs / add Star Wars to filtered list

[fisher-alice]

This PR refines our filtering for K-5 'open-ended' projects by only including input fields with keys that indicate user-generated text (excluding dropdown options). We recently received a Zendesk report that a project was blocked from sharing due to the animation name 'grasshopper_1'. Thus, we are updating the filtering logic to only include user-generated text.

We currently only filter Play Lab projects if they include a field name in USER_ENTERED_TEXT_INDICATORS . When I first implemented filtering of other Blockly project types, I was unsure which field names mapped to user-generated text. When curriculum writers create Blockly blocks, they also determine the field names. So currently we filter all text that is considered user input including dropdown options.

Therefore, @mikeharv and I audited all blocks (https://levelbuilder-studio.code.org/pools) to collect the list of field names that indicate open text (strings) as opposed to dropdown options across all Blockly project types (this took a bit of digging and testing).

While going through all the blocks, we realized that Star Wars's setScore block uses a string parameter that is displayed at the top of the visualization when the program is run. Thus we're adding Star Wars Blockly to list of programs to filter.

Example:

This update is based on the fact that any block field that supports open text has a field name included in the list above. Thus, we follow up and warn/prevent curriculum writers from making new free-text blocks that break this convention. Thanks Mike!.

Before update

Sprite Lab project being flagged for 'grasshopper_1':

Star Wars project that contains profanity not being flagged:

After update

Sprite Lab project with 'grasshopper_1' animation no longer being blocked from sharing:

Star Wars project that contains profanity blocked from sharing:

Links

• Jira: https://codedotorg.atlassian.net/browse/SL-1324
• Slack thread

Testing story

Tested locally on different project types (Sprite Lab, Poetry Lab, Play Lab, and Star Wars (blockly). See before/after updates above.

Deployment strategy

Follow-up work

• Remove createTextArrow_ overrides in Google Blockly
• Validate text field names when editing blocks in pools

Privacy

Security

Caching

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