[needs design] Add workflow for user removal of mistakenly applied labels

❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Observed behavior

On Studio, when applying metadata, due to our decision to have the checkboxes always be "additive", there is no way to remove or replace a mistaken metadata label (for example, choosing "math" instead of "science".)

Expected behavior

We should update the current workflow not to have the checkboxes be dynamic (technically complicated), but so that there is a second complimentary workflow within the modals for removing current selections.

The labels of things that you are allowed to remove should be a flat list labels, based on your current selection (and not an aggregate of potential descendant nodes).

For example, if you have selected a folder called "Math" with the labels "Math" and "Algebra" on that folder, but you want to remove "Algebra" because this should be applied to a child folder instead, the list should be "Math", "Algebra", NOT a collection of all of the labels on the descendant nodes (which might be more specific based on sub folders - like Trigonometry, Geometra, Numeracy, etc)

Perhaps there is a way that we can separate the chips list at the top from the tree selection at the bottom?

User-facing consequences

You can't remove mis-applied metadata, which may discourage people from using the feature more broadly.

Additional information

Steps to reproduce the issue

1. I have a folder of math content (containing sub folders and also resources)
2. I use the bulk editing to apply the "Mathematics" category, and when doing so, and choose the option to save to descendant resources/folders
3. Then, I want to remove the "Mathematics" category because I made an error and it was supposed to be science
4. BUT, when I do that, the original folder that I selected to apply the metadata continues to have the "Mathematics" label

Usage Details

Current Studio May 2025

No files, tests, or entry points are named. Start by locating the bulk-edit metadata modals and reviewing the proposed separate chips and tree-selection workflows. Done means a user can remove labels from the current selection without using descendant labels, while preserving the existing additive workflow.