Use CCM::TextRender instead of CAF::TextRender in RegexpTest

[stdweird]

Use CCM::TextRender instead of CAF::TextRender in RegexpTest; the unittests now can also test with element instances.

Some other minor related modifications

• a convenience method set_json_typed to enable json_typed (together with a get_json_typed to check the current setting)
• an advanced option to overrride the module and contentspath via regexptest flags (useful to test rendering of the /-element); but this should considered an exception.

[hpcugentbot]

Refer to this link for build results (access rights to CI server needed):
https://jenkins1.ugent.be/job/maven-tools-pr-builder/45/
Test FAILed.

[stdweird]

@jrha this needs quattor/CCM#51 to pass the tests, is based on #52 and is a requirement for quattor/configuration-modules-core#475

i'm also tagging this 15.4

[hpcugentbot]

Refer to this link for build results (access rights to CI server needed):
https://jenkins1.ugent.be/job/maven-tools-pr-builder/46/
Test FAILed.

[hpcugentbot]

Refer to this link for build results (access rights to CI server needed):
https://jenkins1.ugent.be/job/maven-tools-pr-builder/47/
Test FAILed.

[stdweird]

test this please

[hpcugentbot]

Refer to this link for build results (access rights to CI server needed):
https://jenkins1.ugent.be/job/maven-tools-pr-builder/48/
Test PASSed.

[jouvin]

@stdweird I have the feeling that some of the commits are related to JSON type support not really to CCM:TextRender. Am I right? In this case, it would be good to adjust the title of the PR...

Also, it would be good to have a short description of the goal of the PR... Not really obvious without an explanation! (I have no doubt it is useful)

Else LGTM.

[stdweird]

@jouvin i updated the PR description. i'm afraid that it will only become really clear why this is relevant when i update quattor/CAF#84 with the CCM::TextRender features that are part of 15.4

the json_typed fixes are relevant for any testing which requires typed data, which requires CCM::TextRender.