fix(notebooks): correctly update pipeline information

[lorenzo-cavazzi]

This addresses an annoying bug happening in the following situation

• the user tries to start an interactive environment from a commit where all the pipelines/jobs related to building the Docker image are available.
• later, the user selects another commit where the pipeline or the job is not found

In this case (as well as a couple of similar combinations), the information about the Docker images availability wasn't updated correctly.

Testing: the easiest way to reproduce the issue is to fork a project, then try to select an older commit -- the pipeline to build the Docker image exists only on the latest commit on the master branch

fix #590

[rokroskar]

doesn't this close #590?

[lorenzo-cavazzi]

doesn't this close #590?

it does, there is a "re #590" in the description but I guess re is not a valid keyword in Github. Let me change it to fix