Enh/77 fmu tools page

[StephanieKemna]

Description

Resolves #77

Add a README to Examples page, add generated FMU files for examples.

Developer Checklist (before requesting PR review)

• [n/a] My code follows the style guidelines of this project
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

I have:

• [n/a] commented my code, particularly in hard-to-understand areas
• performed a self-review of my own code
• not committed unnecessary formatting changes, thereby occluding the actual changes (e.g. change of tab spacing, eol, etc.)
• made corresponding changes to the documentation
• added change to CHANGELOG.md
• [n/a] added tests that prove my fix is effective or that my feature works (for core features)

Reviewer checklist

I have:

• have performed a review of the code
• tested that the software still works as expected
• checked updates to documentation
• checked that the CHANGELOG is updated

[KristofferSkare]

Looks good!

Just thinking if we should fix issues with the generated source files in this same PR or if we should make a new one to fix them.