Feature/355 select multiple component

[g-saracca]

What this PR does / why we need it:
Adds new Select Multiple component to the Design System.

Which issue(s) this PR closes:
Closes #355

Special notes for your reviewer:
Also export some form elements interfaces to solve a ts errors issue when building the design system about FormGroup trying to access private types.
Also add props to existent Select component.

Suggestions on how to test this:

Test the component in storybook.
Check Isolated Select Multiple component in Storybook

Check Select Multiple component within a form in Storybook.

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

Is there a release notes update needed for this change?:
CHANGELOG in the Design System package has been updated.

Additional documentation:
No.

[coveralls]

coverage: 97.424% (+0.09%) from 97.335%
when pulling 5a12f28 on feature/355-select-multiple-component
into 774661b on develop.

[ekraffmiller]

This looks really good! I don't have any requested changes in the code, but I noticed a behavior in the Story that I think could be improved. When you type in the search to get a subset of items, then click the select all checkbox, it selects all the items in the list, not just what you selected, which seems a little unexpected.
For example:

Screen.Recording.2024-05-02.at.9.10.55.PM.mov

[g-saracca]

Nice catch ellen! thanks!
I've refactored the way it behaves a bit, covering more edge cases and added more tests for each of them.

[ekraffmiller]

looks good! approved!

[GPortas]

I'm facing the same error that @ekraffmiller initially detected. When I select all items based on a query string, all items without filter are selected. This happens in both stories.

Screen.Recording.2024-05-06.at.10.48.13.mov

Screen.Recording.2024-05-06.at.10.50.54.mov

[g-saracca]

Hi @GPortas , the initial storybooks links from the PR description are outdated, they have the code before the changes requested by @ekraffmiller.
Here is the last storybook build with the latest changes, please review it here.
I was really convinced that action of chromatic deployment running on same PR was going to replace latest build on the same url than before.