Security::OrchestrationConfigurationRemoveBotWorker add guard to check for existing policies

When a security policy project is removed, we schedule a worker that removes all security policy bots from related projects. We don't cover the case when a project is affected by more than one security policy project so we might remove a bot even though the project should keep it.

To fix this, we can add a guard clause to Security::OrchestrationConfigurationRemoveBotWorker that checks if the project is affected by any security policy project.

This is not a bug because security policy bots will be created on demand, but we can get rid of some necessary transactions by not deleting and re-creating bots.