feat:Add support for Technitium DNS

[justadri]

What this PR does / why we need it?
It adds support for Technitium DNS server (a popular self-hosted option) for ACME DNS challenge.

Summary of your change
Simply exposes the Technitium functionality from the Go-ACME Lego library and adds its configuration to the Websites/Certificates/DNS Providers UI.

Please indicate you've done the following:

• Made sure tests are passing and test coverage is added if needed.
• Made sure commit message follow the rule of Conventional Commits specification.
• Considered the docs impact and opened a new docs issue or PR with docs changes if needed.

Does this PR introduce a user-facing change?

Added support for Technitium DNS in Websites/Certificates/DNS Providers

[f2c-ci-robot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Details

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-sigs/prow repository.

[f2c-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Details

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

[justadri]

/release-note-edit

Added support for Technitium DNS in Websites/Certificates/DNS Providers

[f2c-ci-robot]

@justadri: You must be an org member to edit the release note.

Details

In response to this:

/release-note-edit

Added support for Technitium DNS in Websites/Certificates/DNS Providers

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-sigs/prow repository.