Manually trap web-ext return code to avoid throwing when uploading to the Mozilla store

[philipp-spiess]

Currently, whenever we publish a new browser extension version to the Mozilla store, the script fails even though the upload succeeds. This causes noise in our CI system and confusion amongst engineers.

This "fixes" this based on best practices from this thread (we can't adopt the web-ext-submit script but this is applying a similar pattern directly in our bash script).

Test plan

Exit propagation works:

The rest we have to try and see the next time we publish an extension?

App preview:

• Web

Check out the client app preview documentation to learn more.

[sg-e2e-regression-test-bob]

Bundle size report 📦

Initial size	Total size	Async size	Modules
0.00% (0.00 kb)	0.00% (0.00 kb)	0.00% (0.00 kb)	0.00% (0)

Look at the Statoscope report for a full comparison between the commits 0cd8a3f and 433da06 or learn more.

Open explanation

• Initial size is the size of the initial bundle (the one that is loaded when you open the page)
• Total size is the size of the initial bundle + all the async loaded chunks
• Async size is the size of all the async loaded chunks
• Modules is the number of modules in the initial bundle

[fregante]

we can't adopt the web-ext-submit script

How come?

[philipp-spiess]

@fregante I’m afraid I don't remember 😞 I should've added more context, my bad.