Description

This PR is part of a suite of PR which would make a refactor in the repository examples.
It is intended to apply to most of the examples, by making them homogeneous, more understandable, and more specific to the case they were meant to be.

In this configuration example, the key changes are:

• include also dataReader/Writer profile name as args
• include LargeData as an option (builtin transport argument)
• include ALL previous QoS examples:
  • Deadline
  • Disable positive ACKs
  • Lifespan
  • Liveliness
  • Ownership (strength)
  • Partitions
• Implement all callbacks

The following changes apply to this and the remain examples:

• remove the DDS prefix from the binaries
• snake case in binary names and directory names
• launch only one endpoint per binary (always running them in different shells)
• unify args names and utility
• write proper README.md with the purpose of the example and expected inputs, outputs, behavior… (do not include options in readme → enhance user to run --help )
• implement listener callback in the same class (inheritance)
• include initialization ( init() ) methods in the constructors
• improve parsing options to be a black box to the user

Contributor Checklist

• Commit messages follow the project guidelines.
• The code follows the style guidelines of this project.
• 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
• Any new/modified methods have been properly documented using Doxygen.
• Changes are ABI compatible.
• Changes are API compatible.
• New feature has been added to the versions.md file (if applicable).
• N/A New feature has been documented/Current behavior is correctly described in the documentation.
• N/A Applicable backports have been included in the description.

Reviewer Checklist

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