fix(docs): match the revert example revision to its own record timestamp

The revert response example carried a revision token encoding
2026-01-16T09:12:00.000Z while its file and version showed
2026-01-15T10:30:00Z. A revision is base64url(fileId:contentUpdatedAt), so
the token has to name the record it ships with; every other example in the
document already pairs them, and the one using the later timestamp overrides
updatedAt to match. Echoing the old example back as expectedRevision would
have named content the response never described.

Author: waleedlatif1

apps/docs/openapi-v2-files-audit.json

@@ -4981,7 +4981,7 @@
                 "updatedAt": "2026-01-15T10:30:00Z",
                 "supersededAt": null
               },
-              "revision": "d2ZfVjFTdEdYUjh6NWpkSGk2Qm15VDkxOjIwMjYtMDEtMTZUMDk6MTI6MDAuMDAwWg"
+              "revision": "d2ZfVjFTdEdYUjh6NWpkSGk2Qm15VDkxOjIwMjYtMDEtMTVUMTA6MzA6MDAuMDAwWg"
             }
           }
         ]

apps/sim/lib/api/contracts/v2/openapi/files-audit.ts

@@ -644,7 +644,7 @@ const declaredRoutes = [
                 source: 'revert',
                 restoredFromVersion: 3,
               },
-              revision: 'd2ZfVjFTdEdYUjh6NWpkSGk2Qm15VDkxOjIwMjYtMDEtMTZUMDk6MTI6MDAuMDAwWg',
+              revision: 'd2ZfVjFTdEdYUjh6NWpkSGk2Qm15VDkxOjIwMjYtMDEtMTVUMTA6MzA6MDAuMDAwWg',
             },
           },
         ]