Use ForwardModelStep class

[adnejacobsen]

A PR in Ert is introducing a ForwardModelStep class that allows for pre-experiment and pre-realization validation.

Using these new features we can check if the user is authenticated when launching Ert.

I have looked at this PR in semeio for how to set this up.

I have kept the old SUMO_UPLOADER Ert config, but I suspect it can be deleted. I have only tested the validation part of this locally and have not confirmed that the uploader still functions as expected. We will have to do some more testing on RGS when these features are available in Ert.

[adnejacobsen]

Also: I have not been able to pickup the value of SUMO_ENV when defined using the DEFINE keyword. It only shows up in private_args if passed directly to the SUMO_UPLOAD forward model (SUMO_UPLOAD(<SUMO_ENV>="dev")).

Current solution: check for SUMO_ENV and default to prod if not found. This means that if someone has DEFINE <SUMO_ENV> dev in their config the validation method will check if the user is authenticated to prod and prevent Ert from launching even if the user is authenticated to dev.

[adnejacobsen]

Also: I have not been able to pickup the value of SUMO_ENV when defined using the DEFINE keyword. It only shows up in private_args if passed directly to the SUMO_UPLOAD forward model (SUMO_UPLOAD(<SUMO_ENV>="dev")).

Current solution: check for SUMO_ENV and default to prod if not found. This means that if someone has DEFINE <SUMO_ENV> dev in their config the validation method will check if the user is authenticated to prod and prevent Ert from launching even if the user is authenticated to dev.

Update: The PR in Ert has been merged and some changes have been made. The validate_pre_experiment method now takes a fm_step_json parameter which lets us access the argsList. The argsList seems to be substituted and we can fetch the SUMO_ENV from here.

[adnejacobsen]

The new ForwardModelClass seems to replace the config file, so I have deprecated it. Tested in bleeding and works as expected.

[rwiker]

LGTM.