feat: expose the closeMenuOnSelect option in dropdown component

[12rambau]

This feature have been requested multiple time by memebers of my team at work. I checked a bit on the web and multiple Threads on your forum mentioned it without providing any solution:

• https://community.plotly.com/t/dash-dropdown-select-multi-keep-options-open-after-selection/34576
• https://community.plotly.com/t/keep-the-dcc-dropdown-multi-true-open-when-choosing-a-value-from-options/72542

That's my first contribution to dash so i'm still a bit lost with everything in the repository but I simply tried to expose what is available in the react-select options. I only made changes to the JS exposed options but I'm unsure if I should modify anything from the python side.

I'll move forward with the contributor check list once I'm sure I didn't do anything stupid.

Thanks for your help.

Contributor Checklist

• I have run the tests locally and they passed. (refer to testing section in contributing)
• I have added tests, or extended existing tests, to cover any new features or bugs fixed in this PR

optionals

• I have added entry in the CHANGELOG.md
• If this PR needs a follow-up in dash docs, community thread, I have mentioned the relevant URLS as follows
  • this GitHub #PR number updates the dash docs
  • here is the show and tell thread in Plotly Dash community

[gvwilson]

@T4rk1n is this small enough that we can include it in Dash 3.0, or should we aim for Dash 3.1?

[T4rk1n]

should we aim for Dash 3.1?

For 3.1

[12rambau]

the remaining error is linked to a file that is completely out of scope with this PR and I get the same locally:

dash/_jupyter.py:459:24: E1123: Unexpected keyword argument 'color_scheme' in constructor call (unexpected-keyword-arg)

should I ignoer it or add the apropriate ignore mention ?

[T4rk1n]

💃 Looks good

The CI error was unrelated.

[gvwilson]

thanks @T4rk1n - I'm OK merging with the failed percy tests if you are

[T4rk1n]

thanks @T4rk1n - I'm OK merging with the failed percy tests if you are

The percy tests are flaky, they will require some work to make them more stable.

I'll merge new features to branch release/dash-3.1, fixes going to dev for patch releases.

[12rambau]

You were too fast, I didn't do the changes recommended in the PR instructions (docs and changelog) should I do them in a follow-up ?

[T4rk1n]

You were too fast, I didn't do the changes recommended in the PR instructions (docs and changelog) should I do them in a follow-up ?

I'll handle the changelogs and the docs repo is not public so @LiamConnors will have to take care of it.