Add rsync/graphviz executables and jedi for autocompeletion

[unkcpz]

• rsync is needed for the new backup mechenism.
• graphviz is needed for plot the provenance graph.
• jedi was not a dependency which will make the IPython (verdi shell) autocompletion not work for node.inputs.<tab>.

[unkcpz]

I play around with the milestone because the issue comes with the docker image and I want to use milestone as a "wishlist".The milestones we used to have but not now actively used.
I want to use this PR to start a discussion on who should manage the milestones, when and how often should we make release and which should go to which release. If you think it is better to start a discourse topic for developers (we don't have a channel yet for those discussions), I'll open one to make it more general because me and @danielhollas just started a similar discussion for AiiDAlab.
Pinning @sphuber for comment.

[sphuber]

Think a discourse topic is better suited than a PR, so please go ahead and open one. I will respond there

[unkcpz]

The topic is open in: https://aiida.discourse.group/t/when-to-make-new-releases-how-to-use-milestone/162

[sphuber]

@unkcpz why do we need to install jedi explicitly as a dependency? We install ipython as a direct dependency and that in turn requires jedi:
https://github.com/ipython/ipython/blob/6e37b96b9fa01c78cc529131038e1adc0343e606/setup.py#L188
https://github.com/ipython/ipython/blob/225a1a2699f328c1b4a0ded2de1f7af9f731ad55/setup.cfg#L35

[unkcpz]

Ah, yes, thanks for the correction. The autocompletion is not working when IPython==8.17.2 and jedi==0.19.1. In fact, it is the node inputs not able to autocomplete the attributes. I downgraded the jedi to 0.18.2 and it works.
I think this requires more investigation. I guess it is also reproducible in the local aiida installation. Can you give it a try to specifically install these two versions of dependencies see if you can reproduce it?

[unkcpz]

I think this is the issue related davidhalter/jedi#1962 (a problem for __call__, but for us it is the attributes), if so I think we need to ping the jedi<0.19.

[sphuber]

I think this is the issue related davidhalter/jedi#1962 (a problem for __call__, but for us it is the attributes), if so I think we need to ping the jedi<0.19.

Good detective work. I can confirm that with jedi==0.19.1 it is broken but with jedi==0.18.0 it works. Fine for me to add the pin.