chore: update bot and docs (#3339)

- use latest version: v20240827-2024-08-14-1030-10-geb491d2
- remove specific check number from doc to avoid updating when checks change

Signed-off-by: Caleb Woodbine <calebwoodbine.public@gmail.com>

.github/workflows/verify-conformance.yml

@@ -13,7 +13,7 @@ jobs:
   verify-conformance:
     if: ${{ github.repository == 'cncf/k8s-conformance' }}
     env:
-      IMAGE: gcr.io/k8s-staging-apisnoop/verify-conformance/verify-conformance:v20240814-2024-08-14-1030-6-g354ea7d@sha256:186655142026fab09d6791ce908f0b889ff201c345b342e16fe9d74b6442a66e
+      IMAGE: gcr.io/k8s-staging-apisnoop/verify-conformance:v20240827-2024-08-14-1030-10-geb491d2@sha256:2e72da246c6701d6ee7605b59f688849bb0d2171d208a8469d6ec8258ac9fc7a
     runs-on: ubuntu-latest
     steps:
       - name: write-config

README.md

@@ -51,7 +51,7 @@ Refer to [SIG-Architecture: Conformance Testing in Kubernetes](https://github.co
 
 ### [Verify conformance bot](https://github.com/cncf-infra/verify-conformance)
 
-The bot currently checks 14 [scenarios](https://github.com/cncf-infra/verify-conformance/blob/main/kodata/features/verify-conformance-release.feature) and updates the PR with the results.
+The bot checks several [scenarios](https://github.com/cncf-infra/verify-conformance/blob/main/kodata/features/verify-conformance.feature) and updates the PR with the results.
 This automation provides timely feedback and reduces the time required by the CNCF to confirm that the PR meets all policy requirements.
 
 ### [APIsnoop](https://apisnoop.cncf.io/about)