* Code cleanup, for better understanding

* Further refactoring; text processing to blocks in separate method

* Added unit test for labels - tests standard text and html tags

* Labels added unit tests for markdown

* Further refactoring; made multi and regular handling more congruent

* Interim save, not there yet

* Unit tests done, first working version

* Added test case with two big words

* Code cleanup

* Break up huge words into lines.

* Restore unrelated code change

Call on issue brought to light by #2990.

`ctx` should not be passed as a parameter to the call - not needed and not conform to documentation.
Also cleaned up the calling code to remove the double `fontOptions.chooser()` call.

* Refactor propagateFonts(), first working version. Default font  for 'mono' is now 'monospace'

* Tested and cleaned up refactoring changes

* maximum width constraints must be violated by long words. Fixes #2604.

* chore: moved examples/network/_tests/maximumWidthEdgeCase.html to test/network/

* element characteristic changes
* assume edge color inheritance is correct before choosing
* Adjust nodes’ chosen’s boolean -> bool
* Need to get user-reset size
* make example edges thicker for more noticeable shadow
* preemptive ES6 fix (see #2500/#2501)
* documentation for the feature that was previously overwritten

* Multifont node and edge labels
* adjust documentation
* rework mod-font property inheritance
* Node max/min widths, min heights; Edge max widths
* Accumulate sizes correctly for unconstrained multipoint labels
* handle font.multi when groupOptions.font is not declared
* propagate label fonts on changes, not just creation
* Allow top-level constraint numbers
* accumulate width and empty lines appropriately

Node labels don't currently make use of the 'align' property, so this reuses
the existing property.

The label code has a number of alignment options that make sense to edges only,
so the Edge/Node now passes a boolean to the Label ctor to explain which the label
is being rendered for

Theoretically, there are multiple node shape types that this could apply to.

Will only apply to Network nodes with a shape: 'box' property, as most
other shapes this will not make sense for. This enables the box shape
to be used, for instance, for diagraming CFG data from source code.