Introduce the toolbar parameter at the richtext superclass level, so that formpages created with editors expecting this spec, like ckeditor4, will not fail to load using other editors that do not expect it
Initializing a formfield with an invalid spec fails as expected, however, it appears to leave behind the formfield object, which many automated tests will now consider a failure
Ensure the formfield object is destroyed when reading the spec fails