docs: Add info concerning static assets interception to README

[zernie]

{{PLEASE DELETE ALL PLACEHOLDER VALUES}}

Summary

{{Please provide a brief summary of your work. If this submission is not
referenced by an existing bug or issue, please provide background on what
situation or problem this submission addresses. }}

Related Issue(s)

Issue #{{Issue Number Here}}

Checklist

• Follows Contributing guidelines.
• Pull Request title uses Conventional Commit syntax.
• All tests pass.
• Linted code.
• Authored new tests, if necessary.
• Updated documentation, if necessary.

[DigTheDoug]

Hi, sorry for the delay in responding. Can you provide more detail on this suggestion? I know it's just a readme change but I get conflicting results on whether this is still necessary with the latest version of Cypress or if the Test Isolation changes. Does it work for any browser or is it Chromium dependent? Should the command be placed within each test, or in a beforeAll? Thanks!

[zernie]

@DigTheDoug

1. It is needed with the latest Cypress version.
2. I have only tested with Electron.
3. It should be placed in beforeEach

[DigTheDoug]

Thanks. I would make a couple changes to this or we can just make the changes if you aren't currently able to.

I would mention that this example should be used in case of users having trouble with cached assets (I could not reproduce static assets being cached in browser myself, but I believe that it can happen in cases) rather than it being a default. I would mention that this command is an internal command that is Chrome specific, rather than part of the exposed Cypress API so it's subject to possible change, and I would also mention where in tests it should be, i.e. in the beforeEach.

The PR title should also be changed to use Conventional Commit syntax as mentioned in the PR template; that helps us version releases correctly.