calculation_setups doesn't sync on object modification or deletion

[marc-vdm]

When removing an activity or database, any calculations setups are not updated and may end up containing references to activities that do not exist anymore. This leads to errors when trying to perform a calculation.

I suggest BW checks calculation setups on deletion of activity/database and removes any matching keys from calculation setups.

[cmutel]

Having to iterate over all calculation_setups is not great, but pushing this data to the database needs bigger changes to land first, so we have to...

[marc-vdm]

I agree that this is not ideal, but IMO this should be normal BW functionality.

Note that I forgot that this is the same for impact categories upon their deletion.

And while we're at it, does bw check:

• impact categories when deleting biosphere flows?
• normalization/weighting when deleting impact categories?