feat: Add FQDNs to the subject DNs of TLS certificates

[siegfriedweber]

Description

Add FQDNs to the subject DNs of TLS certificates

Part of stackabletech/secret-operator#617

Definition of Done Checklist

• Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
• Please make sure all these things are done and tick the boxes

Author

• Helm chart can be installed and deployed operator works
• Integration tests passed
• Links to generated (nightly) docs added
• Release note snippet added

Reviewer

• Code contains useful comments
• Code contains useful logging statements
• (Integration-)Test cases added
• Documentation added or updated. Follows the style guide.
• Changelog updated
• Cargo.toml only contains references to git tags (not specific commits or branches)

Acceptance

• Feature Tracker has been updated
• Proper release label has been added
• Links to generated (nightly) docs added
• Release note snippet added
• Add type/deprecation label & add to the deprecation schedule
• Add type/experimental label & add to the experimental features tracker

[siegfriedweber]

A NifiCluster that uses the StandardManagedAuthorizer cannot be easily upgraded. The authorizers.xml file written by the operator has already been processed, and the user with the identity CN=generated certificate for pod was created in the users.xml file. Before the upgrade, it would be necessary to manually add the new subject DNs as users and grant them write access to /proxy.

In my opinion, this change is not worth the hassle of dealing with broken clusters. Therefore, I will probably close this pull request.