#4132: Provide text_format render element

[stefan-korn]

fixes #4132

• Test coverage exists
• Documentation exists

QA Steps

• Add manual QA steps in checklist format for a reviewer to perform to confirm that the feature or fix is working. Include as much details as possible so that the reviewer doesn't lose time figuring out how to perform steps.

[stefan-korn]

Hm, too many return statements in code climate ... seems 4 was acceptable, but 5 are not :-)

Should one switch to "switch" then?

[dafeder]

Picking this back up - I can see where this rule is coming from in the coding standards. It makes it a little harder to read for there to be so many possible returns. I believe if you just have it just set a variable on each condition (call it $string or $return or whatever, and just return that at the end, you should be fine. You may get hit on code complexity for having so many conditions but I am willing to override that in codeclimate since it makes sense to handle this widget that way IMO.

What we will need to bring this in is, you guessed it, text coverage. You were able to provide good test imputs and assertions for what became #4212 do you think you could do the same here? Overall I very much agree with the approach you're taking here -- set it once in the UI schema and do not give the option on the form.