Fix interfering click handlers

[farmaazon]

Pull Request Description

Fixes one failure in #8942 which caught a real issue: clicks at various panels were triggering many handlers at once, often unexpectedly - for example quick clicking at breadcrumbs (and automatic tests always click fast) we could also trigger getting out the current node.

Therefore, I added stopPropagation for all mouse events on "panel" level + where I think the event should be considered "handled" and no longer bother anyone. Also, to unify things, most actions are for click event.

Additionally I spotted and fixed some issues:

• When "clicking-off" Component Browser, it creates new node only if anything was actually typed in (no more dangling operatorX. nodes)
• Filtering now works for operators
• When, after opening CB with source node, user starts typing operator, we replace dot with space
• Fixed our shortcut handler, so it works properly with click event.
• Fixed problems with defocusing input in CB when clicking at links.

Important Notes

I removed PointerMain binding for deselectAll, because it was triggered every time did the area selection.

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

• The documentation has been updated, if necessary.
• Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
• All code follows the
  Scala,
  Java,
  and
  Rust
  style guides. In case you are using a language not listed above, follow the Rust style guide.
• All code has been tested:
  • Unit tests have been written where possible.
  • If GUI codebase was changed, the GUI was tested when built using ./run ide build.

[kazcw]

Do we need a closed event? I think the CB could just emit accepted or canceled.

[farmaazon]

"Closed" means that it lost focus (due to background click, for example). Since this PR, it does differ from direct accept.

[kazcw]

Yes. I don't see the need to increase the complexity of the ComponentBrowser/GraphEditor interface by exposing this distinction to the GraphEditor. The CB could decide whether to emit accepted or canceled internally, and keep anyInputChange encapsulated.