Remove txt-encryption nonce, for prevent issues with txt records deletion

[vsychov]

Description
Fixes #3668

Alternative and better fix is #3735
@szuecs

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vsychov
Once this PR has been reviewed and has the lgtm label, please assign szuecs for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[johngmyers]

I'm wary of this approach. The TXT registry is relying on being able to perfectly reconstruct an identical ownership record and the encryption nonce is breaking this. But disabling an encryption countermeasure seems risky.

Alternative approaches would be to ensure all the old TXT records are stashed away long enough for the deletion code to retrieve them or to save the nonce in a providerspecific property.

But then I think this entire encryption feature is insanity.

[mloiseleur]

Since we will focus on #3901, I close this PR.
/close

[k8s-ci-robot]

@mloiseleur: Closed this PR.

In response to this:

Since we will focus on #3901, I close this PR.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.