Mephisto LIGHT worker task

[JackUrb]

Overview

Following up on #282, this PR updates the task frontend introduced in #281 to now be in a Mephisto-task format. Note, this now requires using Mephisto version 1.0.0.

Implementation

Due to how Mephisto tasks build, I had to rearrange a number of folders, configure webpack, change react versions, etc. to get things running. That's most of the churn of this PR. Additionally:

• Replaces the AppRouter component with a LIGHTAppTaskFrame component, which does the type of routing that a Mephisto task expects. This component is also responsible for requesting the correct authorization key for a given worker, and passing the synthesized URL to the underlying task component.
• Updates the Task component to receive a passed URL and the submit function, though the latter is currently unused right now.
• Creates the Mephisto run_task.py script that actually launches the mephisto job, requiring a preauth_secret that needs to be shared between the server launch and the Mephisto task. This allows Mephisto to sign the worker's auth token properly.

Some notes here, I've left a few messy components in the LIGHTAppTaskFrame file. These should probably be refactored out. Also unfortunately @JustinPinero I expect there to be a significant amount of manual churn merging your onboarding flow, considering some fairly substantial folder thrash required to get Mephisto up-and-running. When you merge onboarding into this, you'll have to add an onboarding_qualification to the local yaml configuration in order to see your onboarding view (after you insert it in the isOnboarding branch of LIGHTAppTaskFrame). See the local_test.yaml file in crowdsourcing/dialogues/multi_party_chat/hydra_confs folder for an example.

Testing

terminal 1>/Users/jju/LIGHT/deploy/web> ./deploy.sh local-no-models rebuild-task
terminal 2>/Users/jju/LIGHT/crowdsourcing/light_gameplay> python run_task.py 

Navigate to the desired location:

[JackUrb]

Just two style nits on this final implementation (related to use of ternaries).

@JustinPinero only thing I think is missing is the change catching "you cant ...." messages to undo do actions.

[JackUrb]

Style nit: Large ternaries are visibly hard to process. As a rule of thumb, if the content of your ternary is larger than a line each for condition, option 1, and option 2, don't put it in a ternary and try to find another way to encode your logic.

The below could be:

if ((MINIMUM_NUMBER_OF_SAYS <= sayCounter) && (MINIMUM_NUMBER_OF_DOS <= doCounter)) {
    const modalContent = ...
} else {
    const modalContent = ...
}
If (url != null) {
    return ...
else {
    return <> null </>;
}

[JackUrb]

Note I'd consider this to be an OK example of a larger ternary, though you'd generally want to group the shorter context together to make this appropriate:

{ (formQuestion == null)
? null
: 
...
}

This helps constrain the context of the ternary such that it's not really deep in the code that you find the alternate branch.