readme: Restructure the readme, improve Getting Started and explanations

[cchudant]

Description

Click to see the rendered version

Restructure the Readme, improve Getting Started and explanations.

Leaving as Draft PR until we can update the "TODO"s

What we may want to change:

• Link to docs may be easy to miss (i think it's ok as long as we can find it easily when we need it)
• Added more links to the documentation, but we may want some more
• I have moved the examples more to the bottom => is it ok or should we display them more
• Rust -> we may want to display it more
• When reading the readme, I can think of some questions one may ask: (i expect them to be the top questions)
  => we may want to put them in the FAQ section in the docs :)
  • Does my CPU work with Intel SGX? Which one are OK? => we may want a whole documentation page about that and link it in the readme
  • What about speed? Is inference slow on a CPU?
  • Want to learn more about how SGX works (technical audience, with lower level explanation that what our blogposts provide)
  • threat model for Intel SGX in general => is this secure against physical attacks and stuff

Related Issue

None

Type of change

• This change requires a documentation update
• This change affects the client
• This change affects the server
• This change affects the API
• This change only concerns the documentation

How Has This Been Tested?

N/A

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I have updated the documentation according to my changes

[cchudant]

i am not too happy with this wording
this may need to move in another section, but I couldn't find any other place that feels natural