feat: add quiet cli arg/module option

[slt]

• Closes Option to disable Cypress the verbose results to stdout #2071

User facing changelog

• There is a new --quiet flag available that will silence any Cypress specific output from stdout.

Additional details

When I saw how noisy our CI was with cypress tests, I assumed by changing the reporter I could make it a little less verbose, but this output comes no matter what reporter is configured.

This pull requests adds --quiet as a option which disables the output for:

• Run Starting
• Spec header
• Video/Screenshots
• Spec results
• Run Finished

This should just leave you with whatever the configured reporter is

How has the user experience changed?

PR Tasks

• Have tests been added/updated?
• Has the original issue been tagged with a release in ZenHub?
• Has a PR for user-facing changes been opened in cypress-documentation? docs: add quiet cli arg/module api flag cypress-documentation#2903
• Have new configuration options been added to the cypress.schema.json?

[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.

[CLAassistant]

All committers have signed the CLA.

[jennifer-shehane]

Very nice. Thanks for the contribution!

We'll want to make sure this covers passing quiet to the Module API also.

We'll have someone from the team more formally review, just noted a typo I found for now.

[slt]

Thank you for taking a look so quickly, I have added a test which verifies the quiet option can be passed in via the module api.

Dismissing my previous review as resolved

[flotwig]

The only functional change that needs to be made is to remove quiet as a config option. Since we want to use it only as a CLI argument/module option, it shouldn't be passed around or exposed as a config var.

[slt]

I can't get the ci jobs to pass consistently, I think it got worse when I merged the develop branch back in, but I don't think these failures are related to my changes

[jennifer-shehane]

@slt Yeah, there is some unrelated flake in those tests that we're working on fixing.

[flotwig]

@slt can you enable this option so I can push a commit to your branch? https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork#enabling-repository-maintainer-permissions-on-existing-pull-requests

going to clean up the run.js code and then merge this

[flotwig]

LGTM. opened a separate PR for minor cleanup #7777

[slt]

Thank you @flotwig @jennifer-shehane