Description of the new feature/enhancement

Currently we dismiss command palette programmatically if user clicks in the bounds of "Tab Content" (second grid row of the terminal page), however if the click is performed outside of these boundaries (e.g., outside of the terminal window or in the tab row) we do not dismiss the palette.

And this is problematic for many reasons.

Here is the simplest example - opening a tab while palette is open leaves it open an without a focus (meaning it can be closed only with mouse):

Same can be achieved by clicking on menu, and then click outside of it (but now you cannot even type)

Same of course happens for the tab switcher

This might might be a root cause for #8319.

The idea here is to close the palette upon focus loss.
There are two approaches to it:

1. Close the palette upon focus loss - this approach is taken in VS Code.

• This approach is more hermetic
• This approach introduces a more significant change in user experience, since now clicking another window closes the palette

2. Close palette when clicking on the tab row (or more precisely on any row of the terminal page which is not the one that palette resides in)

• This will have lesser impact on the experience
• But it will not help us if the focus is somehow lost no by clicking

3. Close palette when tabs items are modified