fix: Watch tab crawl state consistency

[SuaYoo]

Fixes #2059

Changes

• Fixes empty watch tab during some active states
• Disables exclusion and browser window editing while a crawl is stopping
• Refactors frontend crawl states to match backend

Manual testing

Verify with repro steps in #2059

The following should be true:

• Browser Window editing is enabled when a crawl is in any active state that is not stopping
• Exclusions editing and screencast is enabled only when a crawl is in a running state

[ikreymer]

Browser Window editing is enabled when a crawl is in any active state that is not stopping

When a crawl is starting, it was enabled in the menu but the button was disabled, though menu item didn't do anything. I think it should be enabled for starting as well in this case.. I think we can have it be enabled for any state in RUNNING_AND_WAITING_STATES though in some of these it won't have an effect until later, but should be possible to change I think. Users might want to scale down if crawl is waiting for capacity (though it'll still start even if desired scale can't be attained)

[SuaYoo]

When a crawl is starting, it was enabled in the menu but the button was disabled, though menu item didn't do anything. I think it should be enabled for starting as well in this case..

What states are included in isCrawlRunning? That's what the button currently checks. I also see that it's enabled for starting, could you provide more repro steps?

[ikreymer]

What states are included in isCrawlRunning? That's what the button currently checks. I also see that it's enabled for starting, could you provide more repro steps?

Yep, seems to be working now and the other issue also resolved, maybe was running an older version. Looks good!