Remove Cypress from docs for now

docs/manifest.json

@@ -358,7 +358,6 @@
       ["Overview", "/testing/overview"],
       ["Test Emails and Phones", "/testing/test-emails-and-phones"],
       "# Testing Frameworks",
-      ["Cypress", "/testing/cypress"],
       ["Playwright", "/testing/playwright"],
       ["Postman or Insomnia", "/testing/postman-or-insomnia"]
     ]

docs/testing/overview.mdx

@@ -16,12 +16,12 @@ To avoid sending an email or SMS message with a one time passcode (OTP) during t
 Testing Tokens enable bypassing various bot detection mechanisms that typically safeguard Clerk applications against malicious bots, thus allowing test suites to run uninhibited. Without Testing Tokens, you may encounter "Bot traffic detected" errors in your requests.
 
 <Callout type="info">
-  While manually implementing the following logic in your test suite is possible, if you use Playwright you can use our [Playwright integration](/docs/testing/playwright), which will automatically take care of all of this.
+  While manually implementing the following logic in your test suite is possible, Clerk offers a [Playwright integration](/docs/testing/playwright) which will automatically take care of all of this.
 </Callout>
 
 Obtained via the [Backend API](https://clerk.com/docs/reference/backend-api/tag/Testing-Tokens), Testing Tokens are short-lived and valid only for the specific instance for which they are issued. Testing Tokens are only available in development instances.
 
-Upon retrieval, include the token value in a `__clerk_testing_token` query parameter with your Frontend API requests. For instance, a sign-up request using a Testing Token, would look like this:
+Upon retrieval, include the token value in a `__clerk_testing_token` query parameter with your Frontend API requests. For instance, a sign-up request using a Testing Token would look like this:
 
 ```shell
 POST https://happy-hippo-1.clerk.accounts.dev/v1/sign_ups?__clerk_testing_token=1713877200-c_2J2MvPu9PnXcuhbPZNao0LOXqK9A7YrnBn0HmIWxy