dns_active24: rewrite for supporting new v2 API

[xvybihal]

The active24 provider has migrated it's customers to new API that is the same platform as websupport API. There is new V2 DNS API to manipulate DNS records.

Also V1 API interaction is needed to get the id of service, then use the service_id in V2 requests.

This dns_active24 plugin rewrite should fix failing requests for customers, that were already migrated to new API by active24 (migrations started November 2024).

I have made the rewrite as current plugin maintainer showed no interest in doing so.

[github-actions]

Welcome
First thing: don't send PR to the master branch, please send to the dev branch instead.
Please make sure you've read our DNS API Dev Guide and DNS-API-Test.
Then reply on this message, otherwise, your code will not be reviewed or merged.
Please also make sure to add/update the usage here: https://github.com/acmesh-official/acme.sh/wiki/dnsapi2
We look forward to reviewing your Pull request shortly ✨
注意: 必须通过了 DNS-API-Test 才会被 review. 无论是修改, 还是新加的 dns api, 都必须确保通过这个测试.

[xvybihal]

Welcome First thing: don't send PR to the master branch, please send to the dev branch instead. Please make sure you've read our DNS API Dev Guide and DNS-API-Test. Then reply on this message, otherwise, your code will not be reviewed or merged. Please also make sure to add/update the usage here: https://github.com/acmesh-official/acme.sh/wiki/dnsapi2 We look forward to reviewing your Pull request shortly ✨ 注意: 必须通过了 DNS-API-Test 才会被 review. 无论是修改, 还是新加的 dns api, 都必须确保通过这个测试.

Hello, this is my reply

[jursed]

I pulled your PR and tried it out with --renew-all.

First attempt failed after adding the TXT record with this:

The retryafter=86400 value is too large (> 600), will not retry anymore.

I re-ran it with --debug, but the issue didn't reoccur and the cert renewal succeeded. I don't think your changes affect this part of the code anyway. So it looks fine to me.

(It's certainly better than the current state, where acme.sh stopped working on the new v2 API and the plugin maintainer just went ¯\_(ツ)_/¯)

[xvybihal]

@jursed really appreciate anyone testing the new version! Thanks. I briefly checked out the error, I have never encountered it, but to me it seems it is not related to the dns_ plugin itself. It appears to be problem with signing request and not with adding values to DNS via API.