DYN-8045: Fix hanged node search when the user types faster than search

[chubakueno]

Purpose

Currently the node search hangs when the user types faster than the time it takes Lucene to provide results because it is searching in the main UI thread. This PR provides a debouncing algorithm and performs searches sequentially outside of the main UI thread for a smoother search experience. Currently there is no support for cancelling previous search tasks in lucenenet so this is a fix around that limitation

Before fix:

After fix:

Declarations

Check these if you believe they are true

• The codebase is in a better state after this PR
• Is documented according to the standards
• The level of testing this PR includes is appropriate
• User facing strings, if any, are extracted into *.resx files
• All tests pass using the self-service CI.
• Snapshot of UI changes, if any.
• Changes to the API follow Semantic Versioning and are documented in the API Changes document.
• This PR modifies some build requirements and the readme is updated
• This PR contains no files larger than 50 MB

Release Notes

Prevent node search from hanging during fast typing.

Reviewers

@RobertGlobant20
@QilongTang
@sm6srw

FYIs

@avidit

[github-actions]

See the ticket for this pull request: https://jira.autodesk.com/browse/DYN-8045

[sm6srw]

LGTM. But I would like to know what @QilongTang thinks about it.

[chubakueno]

Failed on test DocsAreLoadedFromHostPathBeforeCorePath, but that test never goes through Search or SearchAndUpdateResults, so failure is unrelated.

[mjkkirschner]

@QilongTang this seems to overlap with #15726 am I getting that right? How do you want to proceed with these two prs?

[mjkkirschner]

@QilongTang this seems to overlap with #15726 am I getting that right? How do you want to proceed with these two prs?

@QilongTang after taking a look at this I think I prefer the approach in #15726 - it's behind a feature flag, has tests, avoids locks, and I think is more idiomatic.

I don't know if it solves the issue of the hanging search though - @bendikberg can you verify if it fixes this issue?

[chubakueno]

Improvements in last commit:

• Implemented performance improviments in node library search (side panel)
• Fix library search in case the user uses a combination of two or more modifiers (alt+shift,ctrl+shift,etc)
• Fix library search when user types an empty space
• In context menu is now immediately confirmable on enter. This will help eliminate artificial hardcoded delays in UI Automation testing.

@QilongTang this seems to overlap with #15726 am I getting that right? How do you want to proceed with these two prs?

@QilongTang after taking a look at this I think I prefer the approach in #15726 - it's behind a feature flag, has tests, avoids locks, and I think is more idiomatic.

I don't know if it solves the issue of the hanging search though - @bendikberg can you verify if it fixes this issue?

[github-actions]

UI Smoke Tests

Test: success. 11 passed, 0 failed.
TestComplete Test Result
Workflow Run: UI Smoke Tests
Check: UI Smoke Tests

[chubakueno]

Added unit tests for debouncing.