[23923] Ignore new RTPSParticipantAttributes

[cferreiragonz]

Description

PR eProsima/Fast-DDS#6370 introduces new RTPSParticipantAttributes class. This PR ignores them similarly to the original one.

@Mergifyio backport 2.5.x 2.4.x 2.2.x 1.4.x

Contributor Checklist

• Commit messages follow the project guidelines.
• N/A: 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: Changes are API compatible.
• : 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.

[raulojeda22]

LGTM

[cferreiragonz]

@Mergifyio backport 2.4.x 2.2.x 1.4.x

[mergify]

backport 2.5.x 2.4.x 2.2.x 1.4.x

✅ Backports have been created

Details

• #301 [23923] Ignore new RTPSParticipantAttributes (backport #294) has been created for branch 2.5.x
• #302 [23923] Ignore new RTPSParticipantAttributes (backport #294) has been created for branch 2.4.x
• #303 [23923] Ignore new RTPSParticipantAttributes (backport #294) has been created for branch 2.2.x
• #304 [23923] Ignore new RTPSParticipantAttributes (backport #294) has been created for branch 1.4.x but encountered conflicts

Cherry-pick of 99dc814 has failed:

On branch mergify/bp/1.4.x/pr-294
Your branch is up to date with 'origin/1.4.x'.

You are currently cherry-picking commit 99dc814.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   fastdds_python/src/swig/fastdds/rtps/attributes/RTPSParticipantAttributes.i

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally