Pass options to new private API of builtin mocha reporters.

[patcon]

Addresses: #18014

First off, thanks for this wonderful tool! Sorry for not fully engaging with the really robust process you've laid out, but didn't want to be scared away by my lack of time to engage, and thought maybe someone else would carry it over the line 🙏

Adding this even though not ready for review, so someone else can use-validate (in case it's helpful before I can make time for this process).

---

We're using a private internal mocha API, and it apparently broke:

cypress/packages/server/lib/reporter.js

Lines 292 to 294 in a6a2c49

	this.reporter = new this.mocha._reporter(this.runner, {
	reporterOptions: this.reporterOptions,
	})

• Closes

User facing changelog

Additional details

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?
• 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]

@patcon Thanks for the contribution! Could you please sign our CLA?

We will need some tests written to verify this new behavior. No work can be merged into our project without tests.

There is a Contributing Guide that covers how to contribute and get Cypress running locally here: https://github.com/cypress-io/cypress/blob/develop/.github/CONTRIBUTING.md

Let us know if you have trouble getting the tests running locally.

[jennifer-shehane]

@patcon Do you still have time to address the changes requested in this PR? We will have to close this PR due to inactivity otherwise.