Generators, simplifies storage of txt that is codeEscaped vs htmlEscaped [breaking]

[spacether]

Generators, simplifies storage of txt that is codeEscaped vs htmlEscaped
For documentation on often wants to render text that is html escaped one can do that with {{originalTxt}}
or show the unescaped original content with
{{{originalTxt}}}
And when writing code one want to render txt that it is code escaped like so:
some_variable = {{{codeEscaped}}}

So I am making a java class CodegenText to store properties original and codeEscaped to store values that can be used in those above use cases.

Breaking Change with Fallback

• this is a breaking change with fallback for templates that used description and unescapedDescription
• if one depended on the old string variables, one can switch to the dot method access to get the expected values

PR checklist

• Read the contribution guidelines.
• Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• Run the following to build the project and update samples:

  mvn clean package 
  ./bin/generate-samples.sh
  ./bin/utils/export_docs_generators.sh
  

  Commit all changed files.
  This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
  These must match the expectations made by your contribution.
  You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/python*.
  For Windows users, please run the script in Git BASH.