Optimize challenge handling

[diLLec]

ACME providers seam to have slightly different formats in the Response when validation a process already has started for a domain. To be more flexible on that, this change adds the find_challenges filter plugin which parses the data into a standardized format for the challenge provider task modules.

While other providers always seam to publish the challenges in the challenge_data field of the response, the telesec ACME API will only put the information to challenge_date when the certificate is new or if it has reached it's due date - only that one time. Therefore re-running the module to renew the certificate anytime before the due date or with acme_force_renewal: true will need the token information out of the authorizations field of the response.

I have attached a sample dataset into tests/integration/targets/acme_letsencrypt/find-challenge-filter-plugin.yml for reference.

Alltogether the following changes are introduced:

• adding the find_challenges.py filter plugin which will honor the challenge_data_type
• Create the acme_challenge_data dict in create-challenge.yml
• Use the acme_challenge_data[domain] variable instead of acme_challenge['challenge_data'][domain] in challenge providers

[diLLec]

The test are clean now, except for the http-challenge-local.yml test. The file (located in /tmp) outputs a dns challenge instead of a http challenge as expected. I did not find the file inside of the repository, so I suspect it to be created inside of the github actions somehow. Please support me to fix this.