Allow restriction of which operations are controlled by WBA

I think we should hard code 'update and delete' for now to stop the bleeding and then revisit for configurablity

I think we should hard code 'update and delete' for now to stop the bleeding and then revisit for configurablity
I was just thinking for BC purposes we should keep all operations by default.

Example pushed to the MR

Too fast 🤩 agree to do them both here given you've already done it.
Do we need a simple test for this?

@larowlan sweet! Yeah definitely need a test, just wanted to get agreement on the approach. I was also trying to think of a better name for the config key than just "operations"

Ran in to the same issue with the view revision operation.