chore: webui v2.11.1

[rafaelramalho19]

Bumps to new Webui: https://github.com/ipfs-shipyard/ipfs-webui/releases/tag/v2.11.1

cc #7560

[aschmahmann]

@rafaelramalho19 could you rebase on master, it looks like you have a conflict.

[rafaelramalho19]

@rafaelramalho19 could you rebase on master, it looks like you have a conflict.

Thanks, we'll have to do a new webui release soon, so please don't merge this yet

[lidel]

Update: turned out that fix in ipfs/ipfs-webui#1628 was specific to ipfs-desktop and does not impact use in regular browsers, so there is no need to block go-ipfs on this.

@aschmahmann if you want, feel free to squash & merge as-is (v2.11.0), no need to wait for v2.11.1

[aschmahmann]

@lidel @rafaelramalho19 Have we done some tests with this version of go-ipfs + webui just to make sure everything looks right before merging?

Was hoping to do the full release tomorrow or Wednesday (pending an issue I'm investigating) so if the new WebUI is up by then or you need a bit more time lmk.

[lidel]

Cool, I believe we should have new webui by tomorrow :)
If we don't update this PR by then, feel free to merge as-is.

As for tests, so far all good:

• End-to-end regression tests are green with 0.7.0-rc2
  (we run them CI against the custom binary, config is in .circleci/config.yml#L257-L287)
• I've been using webui v2.11 with 0.7.0-rc2 for about a week without any regressions
  • On top of UI fixes/improvements, the key benefit of this release is that one can import big files without buffering the entire thing in browser's memory. Import of a 2GB video takes a moment, but is no longer crashing my browser.
• I did some manual tests while working on CORS, scenarios right after ipfs init (vanilla state) and custom setup with API running on custom port also work as expected
  • Added E2E tests for those custom setups in ipfs-webui/test/e2e/remote-api.test.js, so we don't need to check manually anymore

[rafaelramalho19]

I've bumped webui version to the latest now