Add possibility to en and disable a cauli instance

[pstued]

As already mentioned in #122, we want to add the possibility to en- or disable a Cauli instance within the CauliViewController. A concrete idea how this could work needs to be defined.

[Shukuyen]

What do you think of this simple mockup:

Cauli enabled

Cauli disabled

[pstued]

In the propsed disable state, it‘s not possible anymore to open the InspectorFloret. I think even though cauli is disbaled, it‘s still handy to use the Displayable Florets. So how about „disabling“ Interceptable Florets by setting the switchs enabled state to false, maybe even update the font color to some grey?!, and add a description that cauli is not intercepting any network traffic anymore. (Not sure how deatailed that should be. But disabling a Floret vs disabling cauli is a difference, so it might be worth mentioning)

What do you think?

[Shukuyen]

I thought it would be strange to still be able to go to the inspector and see a list of (old) records. But with an explanation like you said it should work. And it certainly is a use case to "record" only some requests and then take your time to go through them without having new requests come in.

[brototyp]

What do you think about having the switch in the header of the Interceptable-Floret section. This would make the context and the actual action clearer. Bear in mind that I am just talking about the context. I currently have no idea on how to make that visually pleasing and, more importantly clear.

[Shukuyen]

I think my issue with just disabling interceptable florets is that I always thought about this feature request here in a "Disable Cauli" way. There is a gap between "Cauli is disabled" and "I can still see requests in Inspector" that I had a hard time to get into my head.

Maybe I (we) just need to redefine the feature title from disabling Cauli to stop Cauli recording or similar. By that it's clear what it does and also not an issue that the Inspector is still accessible and has values.