[20650] Examples refactor: Delivery mechanisms

[JesusPoderoso]

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 delivery mechanisms example, the key changes are:

• loans and data-sharing compatible: bounded types, final extensibility.
• use loans mechanism for data management
• add an option to select all delivery mechanisms

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.
• N/A Any new configuration API has an equivalent XML API (with the corresponding XSD extension)
• Changes are backport compatible: they do NOT break ABI nor change library core behavior.
• 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.

[elianalf]

After some tests, we found out that there is an issue when setting the domain in the PubSub participant and the writer and the reader try to communicate through UDP. A deeper investigation is required.

[elianalf]

Suggested change

	case CLIParser::DeliveryMechanismKind::INTRA_PROCESS: // (It should never reach this section
	case CLIParser::DeliveryMechanismKind::INTRA_PROCESS: