Avoid changing custom resource status because of HashSet ordering

When adding the warnings about deprecated fields in custom resources to conditions, we use currently HashSet to store them. But with multiple warnings, HashSet does give unpredictable ordering and that results in the status of the custom resource constantly changing.