Fix logging of matching CA certificate

[jsoriano]

What does this PR do?

When the 'ca_trusted_fingerprint' matches one of the certificates provided, log success only if the matching certificate is actually a CA, otherwise log that the matching certificate is not a CA.

With current code you can find contradictory logs if the matching log is not a CA:

CA certificate matching 'ca_trusted_fingerprint' found, adding it to 'certificate_authorities'
no CA certificate matching the fingerprint

With the changes here, on the same situation this will be logged:

Certificate matching 'ca_trusted_fingerprint' found, but is not a CA certificate
no CA certificate matching the fingerprint

Why is it important?

To avoid confusion due to the contradictory logs.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have added tests that prove my fix is effective or that my feature works (there were tests covering this part).
• I have added an entry in CHANGELOG.md

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-06-08T09:15:26.036+0000

• Duration: 8 min 19 sec

Test stats 🧪

Test	Results
Failed	0
Passed	787
Skipped	11
Total	798

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[pierrehilbert]

LGTM