Editor: make use of minCharCount and clearOnSelection of autocomplete component

[Angi-Kinas]

Description

This PR uses the functionality of the autocomplete component to achieve the following behaviour for the keyword edition:

• When the user chooses a result, the typed characters should be cleaned
• When the user clears the input, the dropdown is closed

Quality Assurance Checklist

• Commit history is devoid of any merge commits and readable to facilitate reviews
• If new logic ⚙️ is introduced: unit tests were added
• If new user stories 🤏 are introduced: E2E tests were added
• If new UI components 🕹️ are introduced: corresponding stories in Storybook were created
• If breaking changes 🪚 are introduced: add the breaking change label
• If bugs 🐞 are fixed: add the backport <release branch> label
• The documentation website 📚 has received the love it deserves

[github-actions]

Affected libs: feature-editor, ui-inputs, feature-dataviz, feature-record, feature-router, feature-search, feature-map, ui-elements, feature-notifications, feature-catalog, ui-catalog, ui-search, ui-layout,
Affected apps: metadata-editor, datafeeder, demo, metadata-converter, datahub, webcomponents, map-viewer, search,

• 🚀 Build and deploy storybook and demo on GitHub Pages
• 📦 Build and push affected docker images

[coveralls]

coverage: 81.764% (-0.02%) from 81.783%
when pulling e589636 on ME-extend-autocomplete-to-clear-input
into decc890 on main.

[github-actions]

📷 Screenshots are here!

[cmoinier]

Thanks for the work :)

However, while the changes work for the second point (closing the dropdown on clear), it doesn't work for the first one. Here I typed "asia" & selected the keyword, but the typed text wasn't cleared.

[Angi-Kinas]

@cmoinier thanks for the review and testing!
You are right, the clearing of the input field did not work after selection. I fixed this now.
While testing I encountered a different bug though.
When selecting a keyword and clicking inside the input field again, the previous selected keyword is being saved as search query and therefore the dropdown suggestions only reflect the previous selected keyword.
This happens just for the keywords (not for the spatial extent keywords).
Until now I could not figure out why this is happening.

[CLAassistant]

All committers have signed the CLA.

[tkohr]

Thanks for the fix @Angi-Kinas ! Works like a charm. Happy to see it needed less logic than expected :-)

[tkohr]

Thanks for the added test! LGTM