Replace existing `editor.actionBar.enabled` setting with new setting that disables editor action bar for specific file types

[juliasilge]

We have turned our new editor action bar on by default and have gotten a fair amount of feedback that it feels a bit awkward for regular source editors, such as .py files, or when making screencasts or teaching with Positron. The main challenge is that for regular source code files, it feels like too much empty space for folks. There is an example in #7241 but this is getting to be very common feedback, including from internal users:

Folks can turn off the new editor action bar using settings:

    "editor.actionBar.enabled": false,
    "workbench.editor.editorActionsLocation": "default",

But if they do that, then some of our core functionality that uses the editor action bar is broken. See for example, the Data Explorer's appearance with these settings:

Plots in an editor tab are also not great under these settings.

I notice that folks' discomfort about the editor action bar is largely for regular source editors. What are some possible options to resolve this widespread discomfort?

• Let the breadcrumb share vertical space with the editor action bar
• Keep editor actions in the VS Code default area on regular source editors
• Unbreak the Data Explorer when "editor.actionBar.enabled": false
• Add more affordances to make the existing space more useful (specifically use space on the left in a legitimately helpful way, or could this be user configurable?)
• Other ideas?

[juliasilge]

We also need to consider the behavior in Zen mode.

[kv9898]

Another vote for sharing vertical space with breadcrumb

[softwarenerd]

The issue here will be "define regular". This means that some piece of code in Positron needs to constantly evaluate the what the currently open / visible editor is, what extensions are running, what commands those extensions are contributing, what context key expressions those commands are using, and what, if any, of those commands want to get displayed on the Editor Action Bar.

[juliasilge]

We're going to take several actions as a result of the feedback from users on this. In this issue, we will track and prioritize fixing the behavior of the editor action bar setting. We are going to remove/replace the editor.actionBar.enabled setting and instead having a setting that disables the editor action bar for certain categories of user-specified files. I hope that we can use the VS Code glob patterns for folks to define these (similar to the files.exclude setting): https://code.visualstudio.com/docs/editor/glob-patterns

As a strawman proposal, we would have folks do something like:

{
  "editor.actionBar.exclude": {
    "**/.R",
    "**/.py"
  },
}

Or something like this totally nuke the editor action bar from all files:

{
  "editor.actionBar.exclude": {
    "*"
  },
}

When we implement this, we want to confirm that the Data Explorer and plots in the editor space do still have their appropriate bars.

[juliasilge]

A few more thoughts:

• We should contribute a setting default for the new setting that disables the editor action bar for .ipynb.
• We'll also need to remove the editor action bar toggling from the "Appearance" menu
• We do not want anything to contribute to the middle anymore, only to left or right.