fix: Don't install jest in circle ci job because of broken 3rd party …

[BlueWinds]

…deps

User facing changelog

No user-facing changes.

Additional details

yargs-parser recently shipped a version with broken / conflicting types. yargs/yargs-parser#452. Because of this, one of our CI tasks (test-types-cypress-and-jest) that npm install jest is failing.

This PR temporarily disables that job, until yargs-parser / jest sort out their problems. @BlueWinds is watching the above issue, and will follow up to re-enable this when it's safe to do so.

Steps to test

CI build passes in this branch, and in no other branches.

How has the user experience changed?

PR Tasks

• Have tests been added/updated?
• Has the original issue (or this PR, if no issue exists) been tagged with a release in ZenHub? (user-facing changes only)
• Has a PR for user-facing changes been opened in cypress-documentation?
• Have API changes been updated in the type definitions?

[cypress-bot]

Thanks for taking the time to open a PR!

• Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
• Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.

[BlueWinds]

Since this a change only to a single circleci task, and that task has now passed, going to merge in without waiting for a completely green build.