Handle access denied file upload error

[szluzero]

WHY are these changes introduced?

Closes https://github.com/Shopify/workflows-operations/issues/3398

Adds error handling for file_uploader to handle ACCESS_DENIED errors for stagedUploadCreate. What the error looks like in prod:

WHAT is this pull request doing?

Instead of the above, we'll now show this:

This PR makes it so that adding bulk_data permissions from admin will allow access of stagedUploadCreate for sqlite files for staff members of a shop that aren't shop owners.

How to test your changes?

Get added to an EA shop but not as owner, make sure you don't have bulk_data_import or bulk_data_export permissions. Then try running an import e.g. pnpm shopify store copy --from-file=test.sqlite --to-store=rusty-development-dev-3

Post-release steps

Measuring impact

How do we know this change was effective? Please choose one:

• n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
• Existing analytics will cater for this addition
• PR includes analytics changes to measure impact

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	77.94% (-0.01% 🔻)	13011/16694
🟡	Branches	72.09% (+0.03% 🔼)	6343/8799
🟡	Functions	78.09% (-0.01% 🔻)	3372/4318
🟡	Lines	78.35% (-0% 🔻)	12321/15726

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟢	... / Dev.tsx	90.59% (-2.35% 🔻)	75% (-1.79% 🔻)	86.36% (-4.55% 🔻)	92.5% (-1.25% 🔻)
🟡	... / admin.ts	75% (-5.43% 🔻)	45.16% (+0.72% 🔼)	90.91%	76.47% (-5.75% 🔻)
🟢	... / file-uploader.ts	89.29% (-0.51% 🔻)	71.88% (-3.13% 🔻)	100%	88.89% (-0.69% 🔻)

Test suite run success

3047 tests passing in 1314 suites.

Report generated by 🧪jest coverage report action from f2fed6f

[github-actions]

We detected some changes at packages/*/src and there are no updates in the .changeset.
If the changes are user-facing, run pnpm changeset add to track your changes and include them in the next release CHANGELOG.

Caution

DO NOT create changesets for features which you do not wish to be included in the public changelog of the next CLI release.

[alexcwatt]

Makes sense to me