feat: webui v2.11.4

[lidel]

https://github.com/ipfs-shipyard/ipfs-webui/releases/tag/v2.11.3
https://github.com/ipfs-shipyard/ipfs-webui/releases/tag/v2.11.4

Sadly #2580 broke E2E tests: we don't see if changing this hash broke anything until we release ipfs-http-server and bump it in ipfs

• manual test (swapped hash in js-ipfs sources of v0.50.2 and looks good)
• figure out how to run webui's e2e tests
  • we test ipfs@next against webui master already (.travis.yml#L260-L265)

[achingbrain]

Can you run E2E tests against the RCs?

[lidel]

Ah, yes, I see the CI end-to-end tests from webui's master against ipfs@next package:

js-ipfs/.travis.yml

Lines 260 to 265 in 8e44e52

	- stage: test-external
	# only run on changes to master
	if: branch = master AND type = push AND fork = false
	name: external - ipfs-webui
	script:
	- E2E_IPFSD_TYPE=js npm run test:external -- -- -- https://github.com/ipfs-shipyard/ipfs-webui.git --deps=ipfs@next

Nvm then, this should be good enough.