Cli enhacement

[caviri]

I added another experimental feature for the CLI. Now, the document IDs are not mandatory to run the executions. But we can use digital twins/executions names, and components tags (component:version i.e. odtp-eqasim:0.2.1 ) to build the pipeline in the CLI.

#93

This opens the door to creating bash scripts to run the whole execution, making it easier to perform full pipeline tests and share executions. Like this:

odtp new user-entry \
--name Ai-1234 \
--email ai@ai.com \
--github ai 

odtp new digital-twin-entry \
--user-email ai@ai.com  \
--name dt-example

odtp new execution-entry \
--name execution-eqasim-test \
--digital-twin-name dt-example \
--component-tags odtp-eqasim-dataloader:0.3.1,odtp-eqasim:0.4.2,odtp-eqasim-matsim:0.1.2,odtp-travel-data-dashboard:0.1.1 \
--parameter-files pa1,pa2,pa3,pa4 \
--ports ,,,8502:8501

odtp execution prepare --execution-name execution-eqasim-test --project-path corsica-dt

odtp execution run --execution-name execution-eqasim-test --secrets-files ,,,se4 --project-path corsica-dt

P.S. If you know a better name for this (component:version) construct, please let me know. I got inspired by how you can pull the images in docker

[sabinem]

@carlos: Let's merge this into develop instead of main. (I just did this: then the CHANGELOG needs to be adapted. I think we should bundle this with some other PRs, such as #97 and a PR to generally only add components by their versions to the Mongo DB. Otherwise we might get a mess in the mongodb. We should then aim to release all these PRs together in a next release this week. Would that work for you?

Also this branch needs a rebase before the dev review: so that the changes are visible.