PITR is enabled and disabled unnecessarily

For setting PBM compression options to take effect, we disable and enable PITR in PBM config but we don't consider if it's enabled in CR at all. This causes PBM to create a lock in pbmLock collection but after PITR is disabled the lock is not released and blocks restores in the cluster. This seems also a problem in PBM, I'll create a ticket for it too.