Only dev/user extension being tested should be loaded in Unit Test windows

[redmunds]

I'm seeing E4B extension in unit test windows:

[peterflynn]

@redmunds When you have the "Extensions" tab selected, extensions are loaded; otherwise, they're not. You could argue we should split that into dev/user extensions in one tab, and default extensions in a different tab, though...

[redmunds]

Yes, it only happens in Extensions Tab.

[marcelgerber]

Isn't it possible to load just the extension being tested and nothing else?

[redmunds]

This is behaving as designed, but updating title for possible improvement. I think the current mechanism would make this easy to implement.

Only dev/user extension being tested should be loaded in Unit Test windows. Note that default extensions should always be loaded.

[peterflynn]

@MarcelGerber That's possible only if you disable the 'run all' option, which by definition has to load all the extensions. And I assume we want to keep that option.

I still think it would be good to just make this a "User Extensions" tab, and then move core-extension unit tests into the Unit & Integration categories with the other core unit tests. That might require build machine changes though, since I think there's a specific Jenkins job set up to run the "extensions" category.