Handle specific exception codes on RCI call.

[BinSquare]

Summary

1. This adds a terminalError wrapper around 2 exception codes that are known to not be recoverable by retrying (this can help avoid retry storm). This data was verified from internal investigation.
2. Separately, it also checks that throttlingError does return exitcode 1 i.e. it will be retried.
3. Refactored from isTransient to isTerminal because the terminal cases are what we want to specifically handle while the default is to delegate to existing retry mechanism for other cases.

Implementation details

Changes are implemented on agent calling RCi.

Testing

Added 2 new tests, one to verify throttlingError returns exitcode 1 + one to verify ClientException will result in exit code 5 i.e. the terminal state for agent.

New tests cover the changes:

Description for the changelog

Terminally exit on unrecoverable RCI exception errors.

Additional Information

Does this PR include breaking model changes? If so, Have you added transformation functions?

No

Does this PR include the addition of new environment variables in the README?

No

Licensing

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[BinSquare]

@amogh09 has a separate PR which will address the static check failure due to the copyright date change from 2024 -> 2025 here: #4461