Do not change the underlying temp object, but instead use an new object 
reference.
This avoids changing references to objects of other elements.

All elements which report the selected index are supposed to send an 
index starting with 1 instead of 0. This a special requirement for the 
analysis of answers.

Since we can't safely assume any other font than the one we ship is 
available, it is better to not allow changing this.

I have not removed the variable completely as in the futire more than 
one font might be wanted. So for now you just can't choose another.

Frames are supposed to be used to group other elements and therefore 
usually needs to be behind them.

Also focus the height input field upon opening the menu.
For the layout menu this does not work as checkboxes don't play nicely 
with menus.

In fact having anything but button in the menu is against the Material 
spec. But i still think this is the best way to achieve the usability we 
want.

- This behaves analogously to the floating marker bar

- Remove element as parameter

For dynamic section we keep the solid line as the dashed one is harder 
to see. Needs to be discussed maybe.

Input elements are now grouped in fieldsets.
They also a cool gradient background color.

Compound elements are now supposed to use overlays for their child
elements. This overlay makes selecting child components (by clicking on
them) and marking them as selected (done by the selection service)
possible.
The SelectionService no longer needs special logic to handle compound
children selection, as they now also have an overlay with the same
interface as normal (canvas) elements.

A few modifications in connected directives are necessary. The now
handle children components in a proper array instead of QueryList.

Likert elements do not have clickable children yet and work a little
differently. This should probably be unitized in the future.

Lower and the input element panel does not show properly.

This way the dialog does not grow too wide, when lots of text is 
entered. There could be a lot more logic here to calculate exactly how 
big the window should be, but that seems like overengineering right now.

- Implement marking buttons as toggle buttons

- 'hideOtherPages' is not supported by verona api
- 'uninterruptible' is already fulfilled by disabling pause and
progress bar

Name changed during development

Do not consider all form elements, but use a list containing only form
elements with validators

Refactor MathKeyboardComponent to reduce code size

Add styles for fixed right position
Customize markup for different positioning
Refactor Usage of KeyboardService in components

Was not working at all before. Now the logic is much simpler with the 
use of tiptap attributes.

Is now able to interpret more stuff from the editor. The only thing 
missing are the list styles.

The default value of 1 MB was too low for the player, which currently
requires 1.18 MB.