The HumioRepository resource has a allowDataDeletion field that is used to prevent accidental deletion. We should add a similar field to other content assets that are managed by the operator. An example of this is the ingest tokens, as deleting a ingest token on the k8s side will result in deleting the ingest token on the LogScale side, but if it's an accidental deletion it can no longer reconcile because the token values will no longer be the same.

For the ingest token example, we should not delete the secret either if the allow deletion attribute is false.