Can't save or run tests on webpack compiled scripts

[ckbedwell]

Problem

If using webpack-compiled scripts that obfuscate the code, we make assumptions on the frontend that it is invalid script when in fact it isn't.

This problem applies to:

1. Script does not export any options
2. Script must set the type to chromium in the browser options.
3. Script must import { browser } from 'k6/browser'

Acceptance criteria

There isn't a clear solution for this problem. The acceptance criteria will be allowing perfectly valid compiled scripts to run and be saved. Potential solutions include:

• Make this validation to be optional or dismissable
• more intelligent detection on the FE that the script is valid (I think this is a giant can of worms...)
• have a sandboxed api that can be called upon to validate scripts

[peterschretlen]

Typically weback will be used with terraform, but still a problem in the UI because the test button cannot be used when the validation we have in place fails.

[peterschretlen]

Related issue: #864
With backend we can do deeper inspection/validation of the script, which will eventually be needed for supporting things like archives (which would be an alternative to using webpack in this case)