[Core feature] Update the Versioning of Entities in Jupyter Environment

[Mecoli1219]

Motivation: Why do you think this is important?

Regarding versioning in Jupyter Notebooks, we are currently creating a new task or workflow for each updated entity since the virtual file path generated by the Ipython kernel will be different. This could mess up the console if someone is frequently developing and updating the code.

Goal: What should the final outcome look like, ideally?

Ideally, if it is the same task or workflow, we should create a new version of the entities instead of creating a new one.

Describe alternatives you've considered

We could probably update the naming of the entities for the Jupyter Notebook environment (ie. by adding the prefix interactive. + base_name of the ipynb file). Regarding versioning, we can use the file name generated by the Ipython kernel as the version of the task or compute it via hashing the code.

All of the modifications described above should only affect the interactive_mode only.

Propose: Link/Inline OR Additional context

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes