stopping fix: backend fixes for #836 + prep for additional status fields

[ikreymer]

• sets 'stopping' field on crawl when crawl is being stopped (both via db and on k8s object)
• k8s: show 'stopping' as part of crawljob object, update subchart
• set 'currCrawlStopping' on workflow
• tests: add tests to test stopping and canceling crawls

operator: additional optimiziations:

• run pvc removal as background task
• catch any exceptions in finalizer stage (eg. if db is down), return false until finalizer completes

crawlconfigs:

• create list of running, running + starting, non running and crawl states in prep for additional crawl state
• treat any running crawl state as running
• update redis keys to match state: adjust redis keys to be more consistent browsertrix-crawler#309 settings (>=0.10.0-beta.2)

[tw4l]

Looks good, thanks for these fixes and the tests!

The CI issue seems to be the same one affecting the test_crawl_timeout nightly test, where the crawl is stopped (in that case due to hitting the timeout) and we'd expect a partial_complete state, but in k3s CI (and seemingly that environment alone) we instead get complete - e.g. https://github.com/webrecorder/browsertrix-cloud/actions/runs/4906101106/jobs/8760308684#step:14:73