fix(firebase_storage): updated firebase_storage_web to allow http package dependency range '>=0.13.0 <2.0.0'. Fixes dependency resolution.

[OutdatedGuy]

Description

Updated the http package to v1.0.0. This will make the plugin compatible with all the packages that use the latest v1.0.0 of the http package.

Related Issues

Fixes #11073

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
• All existing and new tests are passing.
• I updated/added relevant documentation (doc comments with ///).
• The analyzer (melos run analyze) does not report any problems on my PR.
• I read and followed the Flutter Style Guide.
• I signed the CLA.
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• Yes, this is a breaking change.
• No, this is not a breaking change.

[sparrow001]

Seems like there is a clear domino effect taking place, tests are failing because they cant install the packages to test because of the version conflict

Quite ironic

[OutdatedGuy]

Seems like there is a clear domino effect taking place, tests are failing because they cant install the packages to test because of the version conflict

Quite ironic

Yep, as all packages use pub reference instead of path reference. Updating any major dependency seems to fails all the tests.

Unfortunately I don't know how to overcome that issue.

[sparrow001]

Does this mean this will be pushed soon???? :0

[felangel]

LGTM seems like the one failing test could be flaky so I’d try re-running it.

[OutdatedGuy]

Why is this test still running even after 5 hours? @russellwheatley @lesnitsky

[sparrow001]

Seems like a good old GitHub bug. Its stuck on terminating all the processes, so its safe to assume the actual test was successful at least.

[russellwheatley]

Why is this test still running even after 5 hours? @russellwheatley @lesnitsky

No idea, it passed but never left the "in progress" state. Just a bug in Github Actions somewhere.