Temporarily disable configuring auth with secrets

package/auth.yaml

@@ -1,39 +1,6 @@
 version: '2023-01-30'
 discriminant: spec.credentials.source
 sources:
-  - name: Secret
-    docs: |
-      # Storing Credentials as a Kubernetes Secret
-
-      GCP credentials may be supplied as a Kubernetes `Secret`. Credentials will
-      be stored in this control plane and will only be accessible to installed
-      providers.
-
-      Credentials should be provided in the following format as a GCP Service Account keyfile:
-      ```
-      {
-        "type": "service_account",
-        "project_id": "PROJECT_ID",
-        "private_key_id": "KEY_ID",
-        "private_key": "-----BEGIN PRIVATE KEY-----\nPRIVATE_KEY\n-----END PRIVATE KEY-----\n",
-        "client_email": "SERVICE_ACCOUNT_EMAIL",
-        "client_id": "CLIENT_ID",
-        "auth_uri": "https://accounts.google.com/o/oauth2/auth",
-        "token_uri": "https://accounts.google.com/o/oauth2/token",
-        "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
-        "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/SERVICE_ACCOUNT_EMAIL"
-      }
-      ```
-
-      See the [GCP
-      documentation](https://cloud.google.com/iam/docs/keys-create-delete)
-      for more information on how to generate credentials.
-    additionalResources:
-      - type: Secret
-        ref: spec.credentials.secretRef
-    showFields:
-      - spec.credentials.secretRef
-      - spec.projectID
   - name: Upbound
     docs: |
       # OpenID Connect (OIDC)