[BUG] [ASCIIDOC] Asciidoc generator sets not defined example values as string value "null"

[karlo0]

The Asciidoc generator writes for not defined example values of e.g. model attributes the string value "null" instead of leaving it empty.

Furthermore, override the toRegularExpression method to avoid additional escapes of e.g. \ -> \\, -> \ in regular expressions by skipping calling the submethod escapeText.
Note: We don't need additonal escapes in regular expressions for the asciidoc generator since we want to print the plain regular expression as it is in a doc file.

This PR closes Issue #17149.

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:

  ./mvnw clean package || exit
  ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
  ./bin/utils/export_docs_generators.sh || exit
  

  (For Windows users, please run the script in Git BASH)
  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/java*.
  IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
• File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

@JkbLskw

[wing328]

the change makes sense. thanks for the contribution.