do-know
request_certificate does not properly retry when finalize status is processing
If finalize returns back the status 'processing', instead of retrying the finalize request again, the client should instead, make a request to the order resource to verify it's state.
See RFC https://datatracker.ietf.org/doc/html/rfc8555#section-7.4 Page 48:
... The client should then send a POST-as-GET request to the order resource to obtain its current state. The status of the order will indicate what action the client should take (see below).
If a request to finalize an order is successful, the server will return a 200 (OK) with an updated order object. The status of the order will indicate what action the client should take:
o "invalid": The certificate will not be issued. Consider this order process abandoned.
o "pending": The server does not believe that the client has fulfilled the requirements. Check the "authorizations" array for entries that are still pending.
o "ready": The server agrees that the requirements have been fulfilled, and is awaiting finalization. Submit a finalization request.
o "processing": The certificate is being issued. Send a POST-as-GET request after the time given in the Retry-After header field of the response, if any.
o "valid": The server has issued the certificate and provisioned its URL to the "certificate" field of the order. Download the certificate.
