Update (technical) documentation and move to WIKI

[Carsopre]

Ra2ce version checks

• I have checked that the issue still exists on the latest version of the docs in master here.

Kind of issue

Documentation is wrong

Location of the documentation

• README
• Official documentation
• Installation development mode
• Docker and cloud
• Contributing
• Technical meetings
• Technical documentation
• Examples

Documentation problem

1. README.md does not include the link to the pypi release
2. Our official documentation contains information that is non-relevant information for regular ra2ce users (non-developers or those who do not extend ra2ce functionality in any way). When this documentation requires changes of any type (including small typos) said changes need to go through the whole review process, potentially leading to conflicts on development branches with more relevant changes. Examples:
   • Installation development mode,
   • Docker and cloud
   • Contributing
   • Technical meetings
   • Technical documentation
3. The list of "Examples" seems to be getting out of hand.
   • Do we want to show ALL those examples to the users?
   • Or just a subset?
   • This directory is used by Binder, which seems to delay the start up of the environment.

Suggested fix for documentation

1. Simply add the corresponding tag to the README file
2. Move the following items into the WIKI pages, allowing for a faster and more dynamic way of maintaining this technical documentation (and more straightforwards as it is MARKDOWN instead of SPHINX formatting.
   • Installation development mode,
   • Docker and cloud
3. Study whether it is possible to move Contributing into a separate tab to the main page similar as the ones of "Code of conduct" or "License".
4. Discuss the options and added value for the Technical meetings section.
   • This one presents the challenge of only being jupyter notebooks, which we want to "persist".
   • Can we link / show the contents of these notebooks directly from a markdown document?
5. Discuss the options and added value for the Technical documentation.
   • Should it be replaced by README.md files per src subproject?
   • Should we move it to the wiki?
   • Should we combine both of the above suggested options?
6. Move ALL the examples to a separate (private) project only for Deltares contributors (including technical meetings from point 2 if they can't be in a wiki page).
   • Leave only in "examples" a very simple curated subset which avoids repetition of functionalities.
   • This implies updating TC so that said repository is picked up for testing.
   • The subset of curated examples should continued to be tested.

[sahand-asgarpour]

I proposed a selection of examples to remain in the Example folder. Crossed-out ones can be moved, in my opinion.

How the list is made:
I grouped the relevant ones by the drawn boxes and one multi-bracket like line (in black). Then, I filtered out the ones that describe a similar feature but use a different mode or method.