fix: remove unreachable CI provider "Shippable"

[MikeMcC399]

This PR removes the obsolete CI provider "Shippable" from being displayed in README.md. No CI results can be displayed from "Shippable" since it is no longer operating.

Background

The former CI provider "Shippable" no longer provides a service.

• https://app.shippable.com/github/cypress-io/cypress-example-kitchensink is no longer reachable.

• http://docs.shippable.com/ is no longer reachable.

• The badge [![Shippable CI](https://api.shippable.com/projects/56c38fdc1895ca4474743010/badge?branch=master)](https://app.shippable.com/github/cypress-io/cypress-example-kitchensink) no longer responds.

• Shippable's GitHub repositories under https://github.com/Shippable have not been updated since September 2021.

• See We’ve Acquired Shippable to Complete DevOps Pipeline Automation From Code to Production February 21, 2019. JFrog stated they would replace shippable with JFrog Pipelines however it seems there is no simple migration from a Shippable workflow to a JFrog Pipelines workflow. JFrog Pipelines would have to be treated like a completely new CI provider.

Further suggested fixes

1. Remove the reference to shippable.yml in Cypress documentation: CI Provider Examples - Remove obsolete CI provider "shippable" from CI example list cypress-documentation#5145
2. Remove the workflow shippable.yml from this repository

Follow-on suggested (breaking) changes

After implementing the previous suggestions, the next steps would be:

1. Remove the orphaned workaround for issue cy.exec does not work on Shippable CI when using our cypress/base image cypress#6718 from cypress/e2e/2-advanced-examples/misc.cy.js in this repository and merge into Cypress
2. Remove the support for "Shippable" as CI provider from Core Cypress

Removing functionality is a breaking change, even though it should theoretically have no practical impact, since "Shippable" is no longer operating. This would probably need to wait until a future suitable major release of Cypress is planned.

[MikeMcC399]

All tests are passing, except the Azure jobs which fails due to

Your Record Key $(CYP..._KEY) is not valid with this projectId: 4b7344

It may have been recently revoked by you or another user.

Please log into Cypress Cloud to see the valid Record Keys.

https://on.cypress.io/dashboard/projects/4b7344

This is an issue with submitting a PR from a fork, not an issue with the contents of the PR itself.

[lmiller1990]

Thanks for this. I agree those breaking changes are not really breaking, but also no rush to remove the associated code.

Let's merge this, thanks!

[cypress-app-bot]

🎉 This PR is included in version 1.16.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀