Disable Functionality When Workspace != Active Config

[dsanders11]

Currently functionality becomes active once a valid Electron checkout is detected, but there's no check that the Electron checkout matches the active config. This is a potential foot gun for new users, who wouldn't realize that the commands they're running aren't on the checkout they're viewing.

To reduce foot guns, only enable functionality when the Electron checkout matches the active config. Watch for active config changes and enable/disable functionality as needed. Terminate any running tasks during these transitions.