sourcing jupyter/bashrc needs to be robust

[robnagler]

Perhaps want to expand to all sourcing in ~/.bashrc so that you know which file has the error. If ~/juptyer/bashrc has an error, then keep going, because user has to get in to fix it. Need to notify user too.

[e-carlin]

Need to add pre_jupyter_bashrc too. We just had a user that couldn't get in due to a bug in that file.

[e-carlin]

Had this happen again.

[robnagler]

I think we need something like this in jupyter radia-run.sh

trap "handle_bashrc_err" EXIT
handle_bashrc_err() {
    move all custom bashrc out of the way
    check that we aren't in a loop with this by looking for the message on the next line
         if we are in a loop not sure what to do except log it to a file in the user's directory (JUPYTER_FAILURE) 
    put an echo in new jupyter/bashrc  that says we did this 
    exit
}

run the rest of the bashrc and right before exec do this
trap - EXIT