Fix/8157 remove cypress from documentation (#552)

* removal of cypress docs part 1

* Deleted
https://stacks.ensono.com/docs/testing/testing_in_nx/testing_with_cypress ✅
asciidoc\testing\testing_in_nx\cypress\cypress_nx.adoc
docs\testing\testing_in_nx\cypress_nx.md

https://stacks.ensono.com/docs/testing/testing_in_nx/cypress_accessibility_testing ✅
\amido.github.io\docs\testing\testing_in_nx\cypress_accessibility_testing.md
\amido.github.io\asciidoc\testing\testing_in_nx\cypress\cypress_accessibility_testing.adoc

* Removed further cypress related pages

* https://stacks.ensono.com/docs/getting_started/setup - Cypress removed from Stacks Plugin table

* Corrected issues with unresolved links in markdown detected by build warnings in md. pages.
Also removed in https://stacks.ensono.com/   the Test Framework element.. which takes user to the redundant/removed stack-cli testing page

* Removed sentence, as the repos has been archived and no longer works" The example is in the scaffolded web app templates: Stacks Webapp Template"
- asciidoc\testing\axe_automated_accessibility_testing.adoc
- docs\testing\axe_automated_accessibility_testing.md (also remove Cypress in line with the md equivalent

Updated inline md. equivalent
- asciidoc\testing\testing_in_nx\frontend_testing_in_nx.adoc

* Removed the Cypress plugins folder from the ascii.doc equivalent.
Removed from both md. and adoc, the Cypress example in the docs/testing/testing_dotnet_selenium page

* Updated - contract_testing_pact page  (removed references to Jest and Cypress and to keep the explanation framework-agnostic.
Update - .spelling and docusaurus.config.js to remove Cypress related stuff

* Removed folder asciidoc\testing\testing_in_nx\cypress and contents

* Removed Cypress pipeline image files - used in docs\testing\testing_in_nx\cypress_nx.md  and adoc  which have already been deleted

* Added some line breaks so page renders nicer

* fix: accidental change of size.

* Reolving PR review comments
Restored bacj the example in dotnet_testing_selenium pages/file
Removed line breaks in frontend_testing_in_nx

* Fix: homepage UI:  Bottom border missing on.  Infrastructure Show Me container, when page width is narrow.

.spelling

@@ -311,19 +311,15 @@ Commitlint
  - ./docs/nx/azure-node/app-insights-deployment.md
 APPLICATIONINSIGHTS_CONNECTION_STRING
 applicationinsightsConnectionString
- - ./docs/nx/cypress/plugin-information.md
 InitGenerator
 InitDeploy
 AccessibilityGenerator
 accessibility.md
 executor.md
- - ./docs/testing/testing_in_nx/cypress_accessibility_testing.md
 webpage
 spec
 e2e.ts
- - ./docs/testing/testing_in_nx/cypress_nx.md
 localhost
-cypress.config.base.ts
 mocha-junit-reporter
 JUnit-style
 junit-report

asciidoc/testing/axe_automated_accessibility_testing.adoc

@@ -8,28 +8,19 @@ keywords:
   - tests
   - testing
   - jest
-  - cypress
   - accessibility testing
 ---
 
 [CAUTION]
 ====
-We recommend and already have support within link:./testing_in_nx/playwright_accessibility_testing.adoc[Playwright for Axe] and link:./testing_in_nx/cypress_accessibility_testing.adoc[Cypress for Axe]!
+We recommend and already have support within link:./testing_in_nx/playwright_accessibility_testing.adoc[Playwright for Axe]!
 ====
 
 == Axe: Accessibility testing
 
-From the Dequeue family of products, we are using link:https://www.deque.com/axe/[aXe] for accessibility testing. When developing, we expect to support WCAG 2.1 Level AA ["wcag21aa"] at a minimum.
+From the Deque family of products, we are using link:https://www.deque.com/axe/[aXe] for accessibility testing. When developing, we expect to support WCAG 2.1 Level AA ["wcag21aa"] at a minimum.
 
 aXe tests are performed on two levels:
 
 1. Rendering the React component and testing with Jest.
-2. Rendering the entire page and testing with Cypress.
-
-=== Cypress: Debugging Axe failures
-
-"When accessibility violations are detected, your test will fail, and an entry titled "A11Y ERROR!" will be added to the command log for each type of violation found (they will be above the failed assertion). Clicking on those will reveal more specifics about the error in the DevTools console."
--- Source: link:https://github.com/avanslaars/cypress-axe#standard-output[cypress-axe#standard-output]
-
-
-For information on how to fix the failure, follow the HelpUrl printed to the console.
+2. Rendering the entire page and testing with Playwright.

asciidoc/testing/contract_testing_pact.adoc

@@ -77,8 +77,7 @@ npm run test:pact-publish
 === Pact stub service
 
 Pact contracts are easily turned into locally running API stubs. They are great
-for use as a simple service to run integration tests against, whether with
-Jest, or with Cypress. This ensures that you can test your application without
+for use as a simple service to run integration tests against. This ensures that you can test your application without
 hitting the actual endpoint, and ensures the same response every time, without
 duplicating mock definitions.