Deactivate zope promises when the neo is expected to be BACKINGUP,
as this makes the zope process crash, which is currently expected.

Deactivating the zope process entirely in that case is not desired
because reactivating it would require updating instance parameters
and reprocessing the partition. Instead, ideally, the zope service
should adapt to the state of the neo.

Also, move zope service from etc/service to etc/run to make it not
be "on-watch", so that when the neo is BACKINGUP and zope crashes,
the partition does not bang and reprocess continuously. This seems
ok because the promise already asserts the service is running.