T66 docs for tags and settings

[frisograce]

Please check the following before creating the pull request (PR):

• Did you run automatic tests?
• Did you run manual tests?
• Is the code provided in the PR still backwards compatible to previous SIMPA versions?

List any specific code review questions
Hi, just saw @TomTomRixRix 's recent comment about wanting more documentation for the tags and settings. Coincidentally I'd already written a little to help me understand it when I first arrived, so I've polished it a little and thought it may help.

Questions:

1. Is this detailed enough?
2. Is it right for it to have it's own documentation file?
3. How do I make it so that the specific Tags documentation is linked?

Provide issue / feature request fixed by this PR

Fixes #66

[TomTomRixRix]

Hi, this is exactly what @seitela and I had in mind when writing the comment in #66. Like this the user has a resource to understand the concept behind these tags and settings. Regarding your questions:

Is this detailed enough?

I would say yes, maybe even a bit too detailed for lazy documentation readers who would only need an abstract to understand the concept. But having some examples is helpful I guess and the reader can still decide if they want to read the entire documentation.

Is it right for it to have it's own documentation file?

If would prefer having a short summary in the README.md like for the Path Management which includes a link to the detailed documentation file. But I think that this is just my personal taste and we might have to discuss this in a meeting to get multiple opinions.

How do I make it so that the specific Tags documentation is linked?

I guess you would like to link this page? I'm not sure but maybe we can set an internal link to this documentation page, however, I don't have any experience with this.

[TomTomRixRix]

I didn't test building the documentation but content-wise it looks good 👍

[TomTomRixRix]

I'm currently working on #29 and refactor all the default settings into the respective adapters so that in the future the user only has to specify settings which deviate from the sensible defaults. We should add this to the documentation once it's implemented.

[TomTomRixRix]

An interesting information about the Settings which I think we should document is whether they are read only or can be manipulated by the simulation modules. For example, currently the simulate method write the currently simulated wavelength into the global settings which is important to know.