HTTPS certificates are not verified when determining if a target site is ready for scanning
What does this MR do?
- Simplifies the check to verify a target site is ready for scanning
- Adds a bunch of tests using a real http/s server to verify functionality behaves as expected
- Removes verification of certificates during the target site check to remove unnecessary pre-scan waiting for invalid certificates
This resolves issue gitlab-org/gitlab#12063 (closed).