[FW][FIX] Composer: weird behavior of autocomplete dropdown

[fw-bot]

Description:

Previously, when users typed "=S" in the composer, clicked outside, then started editing another cell, the autocomplete dropdown remained visible. Similarly, when they typed "=SUM(" and pressed enter, then edited another cell, the function assistant persisted.

This PR addresses the problem by ensuring that state values are set to false whenever the composer is not in edit mode.

Task: : 3789473

review checklist

• feature is organized in plugin, or UI components
• support of duplicate sheet (deep copy)
• in model/core: ranges are Range object, and can be adapted (adaptRanges)
• in model/UI: ranges are strings (to show the user)
• undo-able commands (uses this.history.update)
• multiuser-able commands (has inverse commands and transformations where needed)
• new/updated/removed commands are documented
• exportable in excel
• translations (_t("qmsdf %s", abc))
• unit tested
• clean commented code
• track breaking changes
• doc is rebuild (npm run doc)
• status is correct in Odoo

Forward-Port-Of: #3867
Forward-Port-Of: #3834

[robodoo]

Pull request status dashboard.

[fw-bot]

@dhrp-odoo @rrahir cherrypicking of pull request #3834 failed.

stdout:

Auto-merging src/components/composer/composer/composer.ts
CONFLICT (content): Merge conflict in src/components/composer/composer/composer.ts
Auto-merging tests/composer/autocomplete_dropdown_component.test.ts
CONFLICT (content): Merge conflict in tests/composer/autocomplete_dropdown_component.test.ts

stderr:

13:16:26.272408 git.c:463               trace: built-in: git cherry-pick b9209d41eb7fdb3edcda723946535cc5d4500980
error: could not apply b9209d41e... [FIX] Composer: weird behavior of autocomplete dropdown
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".
----------
status:

Either perform the forward-port manually (and push to this branch, proceeding as usual) or close this PR (maybe?).

In the former case, you may want to edit this PR message as well.

⚠️ after resolving this conflict, you will need to merge it via @robodoo.

More info at https://github.com/odoo/odoo/wiki/Mergebot#forward-port

[dhrp-odoo]

@rrahir, Conflicts resolved! ✅

[rrahir]

@robodoo r+