Add NSS curl 8.0.0 test

[mattia-moffa]

Verifies that curl -v https://example.com/ runs successfully using curl-8.0.0+NSS+wolfPKCS11.

[LinuxJedi]

There is a reason I resisted doing this direct conversion from the Dockerfile, and it is the fact that we are relying on an external service to exist / work. This external service does use some form of flood protection. I managed to trigger it during testing and get my IP temporarily banned. Even if it didn't, it doesn't feel right to me to hit it like this.

Some thoughts on how to solve this:

• Maybe using a GH URL is OK? Given that it is GitHub Actions calling it.
• Maybe start up a basic HTTPS server to test against.

[mattia-moffa]

Agreed. Shall I just replace https://example.com/ with https://github.com/? I feel like setting up an HTTPS server with valid certs in the GitHub action is overkill in this situation, we're relying on APT repositories and on GitHub itself to install the software at the beginning anyway.

[LinuxJedi]

I think that should work

[LinuxJedi]

Nice work. Thanks for caching too.

Context for PR captain: Curl 8.0.0 is used because newer versions removed NSS support. But it makes for a good TLS test.