Update app-pack-gen process to default to Python kernel

[mcduffie]

Godwin/Jay, as part of EMIT workflow development exercise, ran into an issue where they would have to update the process.ipynb to point to ipykernel instead of the project's ISOFIT environment.

Consider overwriting the Users' environment in their notebook to specify the correct kernel using -k option: https://papermill.readthedocs.io/en/latest/troubleshooting.html

[mcduffie]

Possible solution use -k option to papermill:

https://papermill.readthedocs.io/en/latest/troubleshooting.html

[rtapella]

I wonder if this works better with a build script at runtime... like this is a papermill solution but how would this work if you just register an algorithm with a python script, or shell script wrapping your program?

[mike-gangl]

@rtapella this -k option is only needed because we're using papermill to run the notebook. it's a direct result of using the app-pack-generator system. If a user creates their own app-package (like ASIPS), then this wouldn't come in to play- the docker container that is built as part of the app package has all the libraries and run times required (e.g. python, c++, idl, and so on).