docs: update HTTP links to HTTPS in comments and docs (#16551)

* docs: update HTTP links to HTTPS in comments and docs

Replace insecure HTTP reference links with HTTPS equivalents
across source comments, CRD YAML descriptions, configmap
comments, and generated API docs:

- pkg/apis/serving/v1/revision_types.go: upgrade bit.ly ref links
  in ContainerStatuses and InitContainerStatuses comments
- pkg/autoscaler/aggregation/max/window.go: upgrade Wayback Machine
  link in ascending minima algorithm comment
- config/core/300-resources/revision.yaml: upgrade bit.ly ref links
  in containerStatuses and initContainerStatuses field descriptions
- config/core/configmaps/autoscaler.yaml: upgrade bit.ly link in
  activator-capacity algorithm comment
- docs/serving-api.md: upgrade bit.ly href links in generated API
  reference for RevisionStatus fields
- DEVELOPMENT.md: upgrade Google Cloud Console link

/kind cleanup

* running codegen

* removing wrong file

* Remove core.md from PR tracking (keep file locally)

Author: Ankitsinghsisodya

DEVELOPMENT.md

@@ -198,7 +198,7 @@ kubectl -n knative-serving logs $(kubectl -n knative-serving get pods -l app=con
 
 If you're using a GCP project to host your Kubernetes cluster, it's good to
 check the
-[Discovery & load balancing](http://console.developers.google.com/kubernetes/discovery)
+[Discovery & load balancing](https://console.developers.google.com/kubernetes/discovery)
 page to ensure that all services are up and running (and not blocked by a quota
 issue, for example).
 

config/core/300-resources/revision.yaml

@@ -1528,7 +1528,7 @@ spec:
                     The digests are resolved during the creation of Revision.
                     ContainerStatuses holds the container name and image digests
                     for both serving and non serving containers.
-                    ref: http://bit.ly/image-digests
+                    ref: https://bit.ly/image-digests
                   type: array
                   items:
                     description: ContainerStatus holds the information of container name and image digest value
@@ -1549,7 +1549,7 @@ spec:
                     The digests are resolved during the creation of Revision.
                     ContainerStatuses holds the container name and image digests
                     for both serving and non serving containers.
-                    ref: http://bit.ly/image-digests
+                    ref: https://bit.ly/image-digests
                   type: array
                   items:
                     description: ContainerStatus holds the information of container name and image digest value

config/core/configmaps/autoscaler.yaml

@@ -22,7 +22,7 @@ metadata:
     app.kubernetes.io/name: knative-serving
     app.kubernetes.io/version: devel
   annotations:
-    knative.dev/example-checksum: "47c2487f"
+    knative.dev/example-checksum: "c727b3e8"
 data:
   _example: |
     ################################
@@ -172,7 +172,7 @@ data:
     # The `unit` is one concurrent request proxied by the activator.
     # activator-capacity must be at least 1.
     # This value is used for computation of the Activator subset size.
-    # See the algorithm here: http://bit.ly/38XiCZ3.
+    # See the algorithm here: https://bit.ly/38XiCZ3.
     # TODO(vagababov): tune after actual benchmarking.
     activator-capacity: "100.0"
 

docs/serving-api.md

@@ -1476,7 +1476,7 @@ to their respective digests and their container name.
 The digests are resolved during the creation of Revision.
 ContainerStatuses holds the container name and image digests
 for both serving and non serving containers.
-ref: <a href="http://bit.ly/image-digests">http://bit.ly/image-digests</a></p>
+ref: <a href="https://bit.ly/image-digests">https://bit.ly/image-digests</a></p>
 </td>
 </tr>
 <tr>
@@ -1495,7 +1495,7 @@ to their respective digests and their container name.
 The digests are resolved during the creation of Revision.
 ContainerStatuses holds the container name and image digests
 for both serving and non serving containers.
-ref: <a href="http://bit.ly/image-digests">http://bit.ly/image-digests</a></p>
+ref: <a href="https://bit.ly/image-digests">https://bit.ly/image-digests</a></p>
 </td>
 </tr>
 <tr>

pkg/apis/serving/v1/revision_types.go

@@ -145,7 +145,7 @@ type RevisionStatus struct {
 	// The digests are resolved during the creation of Revision.
 	// ContainerStatuses holds the container name and image digests
 	// for both serving and non serving containers.
-	// ref: http://bit.ly/image-digests
+	// ref: https://bit.ly/image-digests
 	// +optional
 	ContainerStatuses []ContainerStatus `json:"containerStatuses,omitempty"`
 
@@ -154,7 +154,7 @@ type RevisionStatus struct {
 	// The digests are resolved during the creation of Revision.
 	// ContainerStatuses holds the container name and image digests
 	// for both serving and non serving containers.
-	// ref: http://bit.ly/image-digests
+	// ref: https://bit.ly/image-digests
 	// +optional
 	InitContainerStatuses []ContainerStatus `json:"initContainerStatuses,omitempty"`
 

pkg/autoscaler/aggregation/max/window.go

@@ -28,7 +28,7 @@ type entry struct {
 }
 
 // window is a circular buffer which keeps track of the maximum value observed in a particular time.
-// Based on the "ascending minima algorithm" (http://web.archive.org/web/20120805114719/http://home.tiac.net/~cri/2001/slidingmin.html).
+// Based on the "ascending minima algorithm" (https://web.archive.org/web/20120805114719/http://home.tiac.net/~cri/2001/slidingmin.html).
 type window struct {
 	maxima        []entry
 	first, length int