Use `collapsed` for `extraText`s

[jvoigtlaender]

From https://github.com/fmidue/output-blocks/blob/e97c5f06a17c5b99f0bed2a733bfbf974304adf3/output-blocks/src/Control/OutputCapable/Blocks.hs#L511-L516

Potentially the extraText field itself should instead of just a Maybe (there is text or none) make more distinctions (there is no text, or there is text that should be displayed directly, or there is text that should be displayed in a collapsible with a certain on/off setting).

[JNAOB]

Since this issue was already resolved in modelling-tasks, what is the recommended approach for this repository?

Is there a plan to reuse or import the implementation that introduces ExtraText, or should we duplicate the solution here?

[jvoigtlaender]

Good question. What is it that would be shared vs. copied? Is it essentially/exactly the following lines?

https://github.com/fmidue/modelling-tasks/blob/caa382c1f0790309744ca87bef6c188782a07627/src/Modelling/Auxiliary/Output.hs#L129-L146

The natural place to put them to exploit a sharing opportunity would be in https://github.com/fmidue/output-blocks.

And I do think it makes sense to indeed put them there. Also because that would probably mean that if the API around these collapsibles changes somewhat (see fmidue/output-blocks#34), the change needs to be done only in one repo, namely that "central" one.

Any other thoughts, @patritzenfeld, @marcellussiegburg?

[marcellussiegburg]

I second moving the code to output-blocks.