Keep changes inside instances sorted by source timestamp [12421] (backport #2182)

[mergify]

This is an automatic backport of pull request #2182 done by Mergify.
Cherry-pick of 38e8d0f has failed:

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

You are currently cherry-picking commit 38e8d0fb7.
  (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)

Changes to be committed:
	new file:   src/cpp/utils/collections/sorted_vector_insert.hpp
	modified:   test/blackbox/BlackboxTestsPubSubHistory.cpp

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   include/fastdds/rtps/history/ReaderHistory.h
	both modified:   src/cpp/fastrtps_deprecated/subscriber/SubscriberHistory.cpp
	both modified:   src/cpp/rtps/history/ReaderHistory.cpp
	both modified:   test/mock/rtps/ReaderHistory/fastdds/rtps/history/ReaderHistory.h

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

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.io/

[JLBuenoLopez]

@MiguelCompany I think CI failures are unrelated to the PR changes but it would be fine if you can check. It would also be nice if you can check the conflict resolution.

[MiguelCompany]

LGTM