Bump cypress-file-upload from 3.5.3 to 5.0.4

Sourced from cypress-file-upload's releases.

v5.0.4

#285 Fix build configuration to properly load external dependencies

v5.0.3

#278 allow setting "lastModified" property

v5.0.2

#265 Do not preserve existing files.

This was fixed in v5.0.1, but incorrect artifact was deployed to npm.

v5.0.1

#265 Do not preserve existing files.

This functionality was making sense when doing chaining calls, but now it is redundant. More than that, it is different from user may experience when doing same actions manually.

v5.0.0

BREAKING: multiple file upload is now available via array of fixtures – chaining calls are not supported anymore (#251) Massive documentation upgrade: #228 #229 #235 #246 #253 #254 #256 #257 Dependencies upgrade: #255 Switch to Github actions: #248

Shout out to @adrienjoly @zephraph @jethas-bennettjones @andrico1234 @paulblyth

v4.1.1

#225 fix cypress v5 error: binaryStringToBlob() no longer returns a Promise. Update the use of binaryStringToBlob() to expect a returned Blob (shoutout to @danielcaballero)

v4.1.0

Huge shoutout and a glass of beer for @josephzidell for becoming project maintainer and making this release happen!

#211 [Typo] in README.md fixtures -> fixture (shoutout to @Ebazhanov) #215 Update Blob use to be compatible with Cypress 5.0 (shoutout to @emilong)

v4.0.7

#198 avoid throwing error if subject element disappears #199 add built-in support for doc, docx, mp3 #200 fix json content upload

v4.0.6

#187 build data transfer object using proper constructor (shout out to @jdcl32 again )

v4.0.5

#184 #186 fix regression bugs, add ability to change file name of uploaded file (shout out to @jdcl32 )

v4.0.4

#170 update index.d.ts #172 add ability to provide mime type

v4.0.3

#169 update types for es6+ targets support

... (truncated)

• f3b4494 v5.0.4
• 7c26b1b Merge pull request #285 from abramenal/feature/fix-bundle
• bbb30c1 chore: fix ci build trigger
• e61e70e test: run tests against plugin bundle
• bace23c chore: update build configuration
• edb15cb v5.0.3
• a4e8420 chore: run CI for fork PRs
• 9c34dde Merge pull request #279 from abramenal/all-contributors/add-anark
• e526dbc Merge pull request #278 from anark/main
• 0f91cc0 docs: update .all-contributorsrc [skip ci]
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)