Use more overview tables for annotations

[henrikt-ma]

This improves the presentation of some sections in the Annotations chapter, by applying the kind of overview table which is used, for example, in 18.7 Simulations.

This change was triggered by me trying to get an overview of the existing annotations, which isn't easy in in the unstructured sections. More sections could be restructured similarly, but I am keeping down the size of this PR by only taking care of two sections in pressing need, and where the transformation is straight-forward.

Also fixing some minor issues which appear to be results of the recent work on formalizing the notation.

[HansOlsson]

Suggested change

	/*literal*/ constant Boolean absoluteValue;
	/*literal*/ constant Boolean absoluteValue = true;

Should keep the default.

[henrikt-ma]

In 3.6 it wasn't clear that there was a default, and I consider the specification of default an accident of the change of notation. Hence, I think we should open a separate discussion about how to describe the default.

[henrikt-ma]

This is now the topic of #3631.

[HansOlsson]

I can understand that this helps, but my concern with adding such tables is that it is a form of duplicated information, which adds a maintenance burden.

[henrikt-ma]

I can understand that this helps, but my concern with adding such tables is that it is a form of duplicated information, which adds a maintenance burden.

Yes, it is a bit of maintenance burden, but at least to me the burden is easily motivated by the tremendous help it provides me when navigating the document.

[HansOlsson]

Language group: looks good, avoids having annotations at different levels in toc.