Avoid error class name mangling in webpack

[fregante]

What does this PR do?

• Reverts #4763: account for error class name namespacing/hoisting in production bundles #4767
• Closes BusinessError subclasses are being reported to Rollbar #4763
• Related to #3722: keep unminified error class names #3731

Discussion

Webpack is mangling the names due to concatenateModules, but we can't expect them to be stable. concatenateModules currently only saves a few KBs (1.09MB -> 1.05MB), so it's not worth keeping it.

Alternative solutions:

• use both a static and instance name: Err {name = 'Err'; static name = 'Err'}
  • TS complains
  • no way to enforce it
• extract the name from the constructor by instantiating it
  • some errors require additional arguments, so we can't safely call new on them

Future solution:

• Deserialize errors into their correct instances; we're still paying the price for using a hack to avoid fixing it
  • Handle custom error constructors with incompatible signatures sindresorhus/serialize-error#72

  • pixiebrix-extension/src/errors/errorHelpers.ts

    Lines 215 to 217 in 65427ee

    	// List all ClientRequestError subclasses as text:
    	// - because not all of our errors can be deserialized with the right class:
    	// https://github.com/sindresorhus/serialize-error/issues/72

Checklist

• Add tests
• Run Storybook and manually confirm that all stories are working
• Designate a primary reviewer

[twschiller]

currently only saves a few KBs (1.09MB -> 1.05MB)

Interesting, I must have done the check locally incorrectly