ci(satp-hermes): added cbdc ci

[pandaio22]

Pull Request Requirements

• Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
• Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
• Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

• Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
• Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

[RafaelAPB]

Blocked by failing pipeline

[AndreAugusto11]

LGTM! But please, check the failing CI actions. run-satp-tests-recovery (I think they should be disabled) and run-satp-tests-integration-docker. These are not failing because of the report, but the tests are actually failing.

[RafaelAPB]

@pandaio22 please rebase so we can merge. @AndreAugusto11 can you please provide your review?

[sandeepnRES]

@pandaio22 Hi, thanks for the PR. Just one comment from me based on the PR guidelines we follow,
Can you make the title of PR as test(satp-hermes) or ci(satp-hermes) instead of feat, because adding a CI job is not a feature that users of Cacti might be concerned about.
All the feat PRs gets mentioned in release notes but test or ci (and some more) gets skipped from release notes, hence this is a strong recommendation.