Replacing instances when changing the security context on a pod

[brownleej]

Changing the security context on a pod can cause its volume to retain files with the old ownership attached to them. While we can continue to read the files, we can see strange behavior with changing file ownership in the atomic writes in FDB. As a workaround for this, we can have the operator replace any pods that have incorrect security contexts. This will ensure that we get fresh pods with clean configuration.