Added missing EventEmitter2 type to Cypress and cy + missing runUrl to Cypress.run() result.

[sainthkh]

• Closes TypeScript: Property 'removeListener' does not exist on type 'cy' #5228
• Closes The CypressRunResult TS interface is missing the runUrl attribute #6087

User facing changelog

• EventEmitter2 types like removeListener, removeAllListeners are added to Cypress and cy.
• Missing runUrl is added to type.

Additional details

Why was this change necessary?

• TypeScript: Property 'removeListener' does not exist on type 'cy' #5228: Unlike on or once, removeListener and removeAllListeners are documented here. But their types didn't exist in index.d.ts.
• The CypressRunResult TS interface is missing the runUrl attribute #6087: runUrl is documented. But type is missing.

What is affected by this change?

N/A

Any implementation details to explain?

• TypeScript: Property 'removeListener' does not exist on type 'cy' #5228: Added eventemitter2 to cli and used import() in index.d.ts.
• The CypressRunResult TS interface is missing the runUrl attribute #6087: N/A

How has the user experience changed?

#5228

Before:

After:

PR Tasks

• Have tests been added/updated?
• Has the original issue been tagged with a release in ZenHub?
• [NA] Has a PR for user-facing changes been opened in cypress-documentation?
• [NA] Have API changes been updated in the type definitions?
• [NA] Have new configuration options been added to the cypress.schema.json?

[cypress-bot]

Thanks for the contribution! Below are some guidelines Cypress uses when doing PR reviews.

• Please write [WIP] in the title of your Pull Request if your PR is not ready for review - someone will review your PR as soon as the [WIP] is removed.
• Please familiarize yourself with the PR Review Checklist and feel free to make updates on your PR based on these guidelines.

PR Review Checklist

If any of the following requirements can't be met, leave a comment in the review selecting 'Request changes', otherwise 'Approve'.

User Experience

• The feature/bugfix is self-documenting from within the product.
• The change provides the end user with a way to fix their problem (no dead ends).

Functionality

• The code works and performs its intended function with the correct logic.
• Performance has been factored in (for example, the code cleans up after itself to not cause memory leaks).
• The code guards against edge cases and invalid input and has tests to cover it.

Maintainability

• The code is readable (too many nested 'if's are a bad sign).
• Names used for variables, methods, etc, clearly describe their function.
• The code is easy to understood and there are relevant comments explaining.
• New algorithms are documented in the code with link(s) to external docs (flowcharts, w3c, chrome, firefox).
• There are comments containing link(s) to the addressed issue (in tests and code).

Quality

• The change does not reimplement code.
• There's not a module from the ecosystem that should be used instead.
• There is no redundant or duplicate code.
• There are no irrelevant comments left in the code.
• Tests are testing the code’s intended functionality in the best way possible.

Internal

• The original issue has been tagged with a release in ZenHub.

[bahmutov]

@sainthkh could you cherry-pick or merge d3c3728 into this branch before I land it, please?

[sainthkh]

@bahmutov Fast-forwarded and fixed typo (rul -> url).

[bahmutov]

very nice, merging

[robcresswell]

Thanks so much! Wasn't expecting such a fast turnaround on an issue. Amazing work