Feature/jpype script migration

[adamkorynta]

• adds in basic smoke test against scripts to ensure API's are reachable from the wheel without moving to integration test territory

[SWF-WM]

Looks good

[krowvin]

looks good x2

The merge-base changed after approval.

[rma-psmorris]

compute_All_Flowgroups and compute_Single_Flowgroup are duplicated across several of the GateFlow scripts. Does it make sense to move these into a shared module rather than defining them as nested functions in each script? If this makes sense and is outside of the scope of this effort, capture it as a ticket? -- Although, capturing as a ticket would have the cat out of the box by the time we revise possibly making it too late to take advantage of.

Note that milestone 4 validates the scripts converted to the JPype workflow.

[adamkorynta]

compute_All_Flowgroups and compute_Single_Flowgroup are duplicated across several of the GateFlow scripts. Does it make sense to move these into a shared module rather than defining them as nested functions in each script? If this makes sense and is outside of the scope of this effort, capture it as a ticket?

The redundant code is purely the logic for error handling, which is the responsibility of individual scripts and not the library. We could write a library method that iterates over an array and then return a list of exceptions, but I don't see a large benefit or reduction in code duplication there (but allows callers to completely ignore errors....).

One other consideration that I don't like all that much is adding into regi_python_logging is a helper like:

@contextmanager
def log_errors(logger, description):
    try:
        yield
    except Exception:
        logger.exception("Error %s", description)

[rma-psmorris]

Also reviewed and approved stacked PRs