Inherit typography styles

## Bug description

Currently on the "Styles"-configuration page most of the typography styles descent from the "Regular" styling.
Meaning if "inherit" in any styling option of a text element is selected then only the styles from "Regular" are applied.

For example the "Header" styles are not used for the headers as seen in the gif.
This effectively renders the other options useless.

To have everything at one place and to actually be able to use the "inherit" option it would be best to see/configure where the inheritance comes from/where it goes to.
A possible solution would be an option to assign the different base types (Footer, Header, Regular or any additional type) to different typography sections e.g. headings and body-types.

This is just a quick idea with the current methods in the DevPortal. If there is a better way/improvements then go ahead.
This option should define where the styles descend to.

This would allow the editor to see where the settings are pointed, could create alternative styles and easily compare them and the editor can use the inherit option more often instead of assigning every setting new.

Currently it is only useable if all the basic settings are in one "typography base type" (again: Header, Footer and Regular) and for future maintainability this is not suitable.

## Expected behavior

The inherit option should correctly inherit from the style settings and it should be clear where to/from the styles came.

---
@AnRei123

Start at the Styles-configuration page and reproduce the typography inheritance behavior described in the issue, including Header, Footer, and Regular base types. Trace how selecting inherit resolves its source; done means inherited settings use the intended style and the editor can clearly see where each style comes from.

Written by the indexing model from the issue text.