Filtered search > User should be able to select all text

User feedback regarding the filtered search component was reported in &7262. This issue is to determine next steps in regards to the intended UX of the component. Review the feedback below and provide UX input/next steps.

Problem

User feedback

• Pressing ctrl+a / cmd+a only selects one word.
• It is expected that all non-token text is selected rather than just one word.

Specific problems

• Plain text strings that aren't part of a key/value pair get separated into nested <div>s (preventing them from being selected together), but this isn't apparent to a user and the expectation is that this is a normal text string in an input and should be able to be interacted with as such.
• It isn't possible to select all with the mouse or keyboard.
• There's a slight shift of the text when it's converted to a nested <div>.

Solution

• Treat text strings here based on the common paradigm that all text can be selected and edited at the same time (regardless of keyboard/mouse input method) and that they shouldn't be parsed into separate elements.
• If a strong still has to be nested within a new element, ensure that there's no visual shift.

Questions

• How does this impact search functionality? Will it search for an exact match of the string, or still be able to parse each term during the search?