[21362] Fail when trying to serialize `std::string` with null characters on its content

[MiguelCompany]

Description

This addresses #69 and #214 by explicitly failing to serialize a string that contains null characters, instead of silently discard the last part of the string.

@Mergifyio backport 2.1.x 1.0.x Note: I'm not sure whether we should backport this to 1.x.

Contributor Checklist

• [x] Commit messages follow the project guidelines.
• [x] The code follows the style guidelines of this project.
• [x] Tests that thoroughly check the new feature have been added/Regression tests checking the bug and its fix have been added; the added tests pass locally
• [x] Any new/modified methods have been properly documented using Doxygen.
• [x] Changes are backport compatible: they do NOT break ABI nor change library core behavior.
• [x] Changes are API compatible.
• N/A New feature has been added to the versions.md file (if applicable).
• [x] Applicable backports have been included in the description.

Reviewer Checklist

• [x] The PR has a milestone assigned.
• [x] The title and description correctly express the PR's purpose.
• [x] Check contributor checklist is correct.
• [x] Check CI results: changes do not issue any warning.
• [x] Check CI results: CI pass and failing tests are unrelated with the changes.

[Mario-DL]

Should be also make the changes when serializing a wstring ?

[MiguelCompany]

Should be also make the changes when serializing a wstring ?

Not sure, the standard says that for strings, the terminating null character is not transmitted. Not sure if that implies that the string can have null characters in the middle. I'd say we can handle that on a different PR

[MiguelCompany]

@Mergifyio backport 2.1.x

[mergify[bot]]

backport 2.1.x

✅ Backports have been created

* [#246 [21362] Fail when trying to serialize `std::string` with null characters on its content (backport #245)](https://github.com/eProsima/Fast-CDR/pull/246) has been created for branch `2.1.x`