Add DNS provider for F5 XC

[ldez]

• adds a description to your PR
• have a homogeneous design with the other providers
• add tests (units)
• add tests ("live")
• add a provider descriptor
• generate CLI help, documentation, and readme.
• be able to do: (and put the output of this command to a comment)

  make build
  rm -rf .lego
  
  F5XC_API_TOKEN="xxx" \
  F5XC_TENANT_NAME="yyy" \
  F5XC_GROUP_NAME="zzz" \
  ./dist/lego -m [email protected] --dns f5xc -d '*.example.com' -d example.com -s https://acme-staging-v02.api.letsencrypt.org/directory run

  Note the wildcard domain is important.
• pass the linter
• do go mod tidy

Ping @Ewouddlb, can you run the command (with your domain, email, credentials, etc.)?

Closes #2408

How to test this PR?

1. You need Go
2. Checkout the PR:

   git clone https://github.com/ldez/lego.git
   cd lego
   git checkout feat/f5xc

3. Compile lego:
   • if you have make: make build
   • if you don't make make: go build -o dist/lego ./cmd/lego
4. Run the following command with your information (email, domain, credentials):

   F5XC_API_TOKEN="xxx" \
   F5XC_TENANT_NAME="yyy" \
   F5XC_GROUP_NAME="zzz" \
   ./dist/lego -m [email protected] --dns f5xc -d ''*.example.com' -d example.com -s https://acme-staging-v02.api.letsencrypt.org/directory run

   The wildcard domain is important
5. Before each run of the command, you should clean your local environment:

   rm -rf .lego

[ldez]

The wrong usage of HTTP code is a problem: technically, a retry should only be done on client errors (4xx) and never on server errors (5xx).
Because server errors should represent real server problems and not the status of the data.

And without the documentation about the field code, it is difficult to know what to do.

[ldez]

I implemented a naive retry, this should help.

[Ewouddlb]

Thanks, that works great. There is one minor error that does popup when trying to clean up the TXT records but the actual records seem to be cleaned up.

[testuser@localhost lego]$ ./dist/lego -m <user> --dns f5xc -d '*.xc.our-test-domain.com' -d xc.our-test-domain.com -s https://acme-staging-v02.api.letsencrypt.org/directory run
2025/03/03 16:07:12 [INFO] [*.xc.our-test-domain.com, xc.our-test-domain.com] acme: Obtaining bundled SAN certificate
2025/03/03 16:07:13 [INFO] [*.xc.our-test-domain.com] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz/187702324/16266991524
2025/03/03 16:07:13 [INFO] [xc.our-test-domain.com] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz/187702324/16266991534
2025/03/03 16:07:13 [INFO] [*.xc.our-test-domain.com] acme: use dns-01 solver
2025/03/03 16:07:13 [INFO] [xc.our-test-domain.com] acme: Could not find solver for: tls-alpn-01
2025/03/03 16:07:13 [INFO] [xc.our-test-domain.com] acme: Could not find solver for: http-01
2025/03/03 16:07:13 [INFO] [xc.our-test-domain.com] acme: use dns-01 solver
2025/03/03 16:07:13 [INFO] [*.xc.our-test-domain.com] acme: Preparing to solve DNS-01
2025/03/03 16:07:14 [INFO] Wait for f5xc create [timeout: 1m0s, interval: 2s]
2025/03/03 16:07:14 [INFO] [xc.our-test-domain.com] acme: Preparing to solve DNS-01
2025/03/03 16:07:14 [INFO] Wait for f5xc replace [timeout: 1m0s, interval: 2s]
2025/03/03 16:07:16 [INFO] [*.xc.our-test-domain.com] acme: Trying to solve DNS-01
2025/03/03 16:07:16 [INFO] [*.xc.our-test-domain.com] acme: Checking DNS record propagation. [nameservers=8.8.8.8:53,8.8.4.4:53]
2025/03/03 16:07:18 [INFO] Wait for propagation [timeout: 1m0s, interval: 2s]
2025/03/03 16:07:23 [INFO] [*.xc.our-test-domain.com] The server validated our request
2025/03/03 16:07:23 [INFO] [xc.our-test-domain.com] acme: Trying to solve DNS-01
2025/03/03 16:07:23 [INFO] [xc.our-test-domain.com] acme: Checking DNS record propagation. [nameservers=8.8.8.8:53,8.8.4.4:53]
2025/03/03 16:07:25 [INFO] Wait for propagation [timeout: 1m0s, interval: 2s]
2025/03/03 16:07:25 [INFO] [xc.our-test-domain.com] acme: Waiting for DNS record propagation.
2025/03/03 16:07:31 [INFO] [xc.our-test-domain.com] The server validated our request
2025/03/03 16:07:31 [INFO] [*.xc.our-test-domain.com] acme: Cleaning DNS-01 challenge
2025/03/03 16:07:31 [INFO] [xc.our-test-domain.com] acme: Cleaning DNS-01 challenge
2025/03/03 16:07:32 [WARN] [xc.our-test-domain.com] acme: cleaning up failed: f5xc: delete RR set: code: 5, message: the requested resource record was not found: (group,name,type) (acme-records,_acme-challenge,TXT)
2025/03/03 16:07:32 [INFO] [*.xc.our-test-domain.com, xc.our-test-domain.com] acme: Validations succeeded; requesting certificates
2025/03/03 16:07:32 [INFO] Wait for certificate [timeout: 30s, interval: 500ms]
2025/03/03 16:07:33 [INFO] [*.xc.our-test-domain.com] Server responded with a certificate.

[ldez]

the cleanup error is expected because I remove the full RRSet related to ACME challenge in one time, so you can ignore it.

[dmke]

LGTM