Fix: DO-3028 'Maximum update depth...' react error in select

[krzysztof-causalens]

Motivation and Context

Issue reported that in some cases Select ends up displaying a 'Maximum update depth...' error.

Reproduced the issue in the internal product but it usually doesn't occur in just local storybook, except when in mobile emulation mode. Research suggested it's likely related to these similar issues:

• Infinite render loop when the toggle button's ref is stored in a state variable downshift-js/downshift#1540
• React v18 + Formik + controlled Downshift Select bug downshift-js/downshift#1511

Some of them seem to be fixed in Downshift v8 or v9 but we're still on v7, didn't want to upgrade now as there's breaking changes to work through and test.

Instead I applied workarounds as suggested in the threads - mainly around memoizing the props produced by the downshift prop getters.

Implementation Description

Any new dependencies Introduced

How Has This Been Tested?

Locally in storybook, after these changes I can't reproduce in mobile emulation mode (except for multiselect for some reason, but that one was not reported as an issue in prod so leaving for now).

Copied over the modified file to internal product, seems to fix the issue there as well.

PR Checklist:

• I have implemented all requirements? (see JIRA, project documentation).
• I am not affecting someone else's work, If I am, they are included as a reviewer.
• I have added relevant tests (unit, integration or regression).
• I have added comments to all the bits that are hard to follow.
• I have added/updated Documentation.
• I have updated the appropriate changelog with a line for my changes.

Screenshots (if appropriate):

[patricia-causalens]

LGTM