[22280] New property to select preferred key agreement algorithm

[MiguelCompany]

Description

DDS security specifies the possibility of selecting the key agreement algorithm used to generate the shared secret at the end of the authentication phase.

The Fast DDS documentation indicates that Elliptic Curve Diffie-Hellman (ECDH) is used, but this is only the case if a participant from other vendor starts the authentication and proposes that method.

This pull request:

1. Changes the default key agreement algorithm to the one indicated in the documentation
2. Adds a new dds.sec.auth.builtin.PKI-DH.preferred_key_agreement property that allows choosing the preferred algorithm to use.

@Mergifyio backport 3.1.x

We will backport to 3.1.x, but leaving the default value of the new property to the old behavior.
We will then backport from there into 3.0.x 2.14.x 2.10.x

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
• N/A Any new/modified methods have been properly documented using Doxygen.
• 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).
• New feature has been documented/Current behavior is correctly described in the documentation.
  • Related documentation PR: [22280] Add documentation for preferred_key_agreement property Fast-DDS-docs#963
• 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.
• If this is a critical bug fix, backports to the critical-only supported branches have been requested.
• Check CI results: changes do not issue any warning.
• Check CI results: failing tests are unrelated with the changes.

[Mario-DL]

Interesting additions. Apart from the comments below, I think it would be interesting to have the possibility of specifying this property in the XML. If the suggestion is accepted, proper XMLParser test should be added.
Also, we would need to pair this PR with the corresponding one in docs

[MiguelCompany]

Apart from the comments below, I think it would be interesting to have the possibility of specifying this property in the XML. If the suggestion is accepted, proper XMLParser test should be added.

Properties are already parsed from the XML. There is no distinction or special processing for the security ones.
On commit c01c29d I have added the new property to the profiles of some of the security communication tests.

[Mario-DL]

LGTM with green CI

[Mario-DL]

LGTM with green CI

[Mario-DL]

LGTM

[Mario-DL]

Ci already full green see here. Rebase conflicts only in versions.md. Marking as RTM

[Mario-DL]

@Mergifyio backport 3.1.x

[mergify]

backport 3.1.x

✅ Backports have been created

• #5442 [22280] New property to select preferred key agreement algorithm (backport #5413) has been created for branch 3.1.x but encountered conflicts