feat(satp): adding feature and test for maxretries and maxtimeout

[sfilangio01]

Introduces a new utility function, executeOperationWithRetriesAndTimeout, which encapsulates retry and timeout logic for SATP step message processing. This update aims to enhance reliability by handling transient failures and timeouts effectively.

Additionally, two new error types are introduced in satp-errors.ts:

1. GatewayRetryOperationError: Thrown when retries are exhausted without success.
2. InvalidStageError: Thrown when an invalid stage is encountered during the SATP process.

Resolves #3744.

Pull Request Requirements

• [ X] 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.
• [X ] 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.
• [ X] Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

• [X ] Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
• [ X] 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.

[LordKubaya]

Could you resolve DCO errors, your commit is not signed.
Set up GPG keys and use git commit -s.

Be careful with the CI errors.

[LordKubaya]

Please do not change how the transfer is executed, errors are not throwing, be careful when we are starting in the middle of a transfer(recovering) because there can be messages already received or created in the session... That code was already done and it should not be deleted.

[sfilangio01]

First of all, thank you for all of your feedbacks and for your review.

Regarding your comments:
1)

Could you resolve DCO errors, your commit is not signed. Set up GPG keys and use git commit -s.

Be careful with the CI errors.

Yes, I already set up the key and signed my first commit, but then there was the problem with the conflicts and that's why we talked yesterday. When I did the commit with you I think forgot to add the signature again

Please do not change how the transfer is executed, errors are not throwing, be careful when we are starting in the middle of
a transfer(recovering) because there can be messages already received or created in the session...That code was already done and it should not be deleted.

As i said before, the errors are indeed thrown (but inside the executeOperationWithRetriesAndTimeout instead of the previous position). I don't know if this was not clear or maybe the code is not super clean, but I also added in the documentation of the code the way it was functioning. If you think it will be better, i can revert to the previous stage and instead of throwing the error in the auxiliary function i can throw it like it was in the previous code.

Thank you again!

[petermetz]

@sfilangio01 It looks like there might be a file with special characters in its name added to the diff. Unless there is a very specific purpose and need for it, I'd like to ask that you remove the :monitor: file.

[RafaelAPB]

@sfilangio01 could you please rebase your branch with the latest satp-dev, and re-test? We would like to incorporate your changes soon

[RafaelAPB]

cc @LordKubaya @AndreAugusto11

The merge-base changed after approval.

[RafaelAPB]

Thank you for your contribution. @sfilangio01 please update the MR, rebasing it as per your availability. Please note that we will close stale MRs to cleanup in a close future.

[AndreAugusto11]

LGTM!

The merge-base changed after approval.