Serving with autoTLS and auto redirect to HTTPS does not work

## What version of Knative?

### 1.1

## Expected Behavior

When a new service is deployed, service URL should be served in HTTP and once HTTPS certificate validation is done, HTTPS and auto redirect to HTTPS should be enabled.

## Actual Behavior

When autoTLS with auto redirect to HTTPS is enabled, the service does not work because before autoTLS verification could be done, auto redirect redirects all requests to HTTPS which does not work because verification for the HTTPS is not yet done.
The service does not become active and certificate validation goes in a infinite loop and it also hits lets-encrypt rate limit.

## Steps to Reproduce the Problem

> The following Knative deployment is done on DigitalOcean Managed Kubernetes cluster
> The Domain DNS records are present in DigitalOcean domains

### 1. Install Knative serving using yaml
```bash
kubectl apply -f https://github.com/knative/serving/releases/download/knative-v1.1.0/serving-crds.yaml
kubectl apply -f https://github.com/knative/serving/releases/download/knative-v1.1.0/serving-core.yaml
```

### 2. Install Kourier network layer
```bash
kubectl apply -f https://github.com/knative/net-kourier/releases/download/knative-v1.1.0/kourier.yaml

kubectl patch configmap/config-network \
--namespace knative-serving \
--type merge \
--patch '{"data":{"ingress-class":"kourier.ingress.networking.knative.dev"}}'

kubectl --namespace kourier-system get service kourier
```

### 3. Direct Knative to use the domain
```bash
kubectl patch configmap/config-domain \
--namespace knative-serving \
--type merge \
--patch '{"data":{"test.voiceintern.com":""}}'
```
### 4. Enabling TLS with HTTP01
```bash
kubectl apply -f https://github.com/knative/net-http01/releases/download/knative-v1.1.0/release.yaml

kubectl patch configmap/config-network \
--namespace knative-serving \
--type merge \
--patch '{"data":{"certificate-class":"net-http01.certificate.networking.knative.dev", "auto-tls":"Enabled", "http-protocol": "redirected"}}'
```

### 5. Deploying sample app and testing
```bash
kn service create hello \
--image gcr.io/knative-samples/helloworld-go \
--port 8080 \
--env TARGET=World \
--revision-name=world
```

> After this step, the output is always
```bash
$ kn services list -A
NAMESPACE NAME URL LATEST AGE CONDITIONS READY REASON
default hello https://hello.default.test.voiceintern.com hello-world 10m 1 OK / 3 Unknown CertificateNotReady : Certificate route-139798f4-02d6-42b9-b7a0-5fdf596dbe5a is not ready.
```

Start by reproducing the issue with the listed Knative Serving, Kourier, and net-http01 releases, then inspect the config-network settings for auto-tls and redirected HTTP traffic. Trace the certificate validation route and redirect behavior. Done means a new service remains reachable over HTTP during validation, then enables HTTPS and redirects HTTP after the certificate becomes ready.

Written by the indexing model from the issue text.