jupyter-vep: Expand details on extensions design

[duyguHsnHsn]

What: Changed the high level design diagram
Why:
Since introducing VDK variables directly is not a high level requirement the iPython package module should be removed from the VEP's high level design. The new diagram for the High level design is much more accurate and gives a better idea of what the changes will be.
The iPython package with the VDK variables can be introduces later on as an enhancement but should not have a place in the bigger picture of VDK Jupyter Integration.

Signed-off-by: Duygu Hasan [email protected]

[antoniivanov]

Please avoid generic titles like "changes on README.md" - I mean every single change on readme could have this title. Let's be explicit, what is the change? E.g "Expand details on extensions design" or something similar.

[antoniivanov]

I missed saying that since it can be done at follow-up PR when you have better idea about these things

But we need to be very explicit here.

What are the exact graphical elements that would be introduced. Having mockup picture would be a huge bonus .

What are the exact request that would be sent and what commands would be supported?

Also there's a lot of assumption about what the reader knows and not everyone reading this would know how VDK works and what is file step plugin and etc , so you need either describe or better link to existing documentation that explain concepts you are using.