fix(SelectionManager): support full collection for select all functionality

[reidbarber]

Closes #9620

When you had a collection with 'all' selected inside an Autocomplete, then filtered down the collection and toggled an item, the 'all' selection internally was only including filtered items' keys, so you'd lose selection for all non-visible items.

This adds a fullCollection field so we can still access the unfiltered collection when toggling selection.

✅ Pull Request Checklist:

• Included link to corresponding React Spectrum GitHub Issue.
• Added/updated unit tests and storybook for this change (for new code or code which already has tests).
• Filled out test instructions.
• Updated documentation (if it already exists for this component).
• Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

Test new story:

1. Filter down the list by typing 'ba'
2. De-select one of the options
3. Clear the field
4. 'Foo' should still be selected

[rspbot]

Build successful! 🎉

• View the storybook
• View the S2 storybook
• View the S2 docs
• View the React Aria docs

[LFDanLu]

This seems to work well for fixed collections, but what do you think about async loaded items or if the wrapped collection has controlled items (i.e. the filtering is handled externally and items constantly changes causing fullCollection to change)? I suppose for that case it would reasonable to expect selected keys to be tracked outside the component itself?

[snowystinger]

(i.e. the filtering is handled externally and items constantly changes causing fullCollection to change)?

I think it'd be good to have some tests for some of these. It'd help me to reason about it.

[rspbot]

Build successful! 🎉

• View the storybook
• View the S2 storybook
• View the S2 docs
• View the React Aria docs