feat(Select): wrapped demo

[kmcfaul]

What: Closes #9511

Investigating different approaches overall but throwing this up for now to start a discussion. The 'boiler plate' code like the arrow handling is trickier than I initially thought it would be to extract because its stateful and specific to the example use case. In the typeahead example the function really is there to calculate which index to put the visual focus on, and not the actual arrow key handler which is running internally in Menu.

How does everyone feel about an approach like this where we effectively turn a demo into a wrapper component that we export for use? This way means a user can use a very simple component that internalizes almost all logic if their use case matches the example, and still has the wrapper code to work from if anything needs to be customized.

Right now the new example code shown in the docs is only importing the wrapper, but we could copy that into the same file to show everything in the one place. I initially had everything in the example file, but was running into an issue with exporting the wrapper directly from the examples folder (still looking into that).

[patternfly-build]

Preview: https://patternfly-react-pr-9726.surge.sh

A11y report: https://patternfly-react-pr-9726-a11y.surge.sh

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.