fix(sdk): Deprecate StepConfig.semantics, add StepConfig.semanticsPerRetry with correct AT_MOST_ONCE behaviour

[nvasiu]

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

Issue Link, if available

#394

Description

Steps configured with StepSemantics.AT_MOST_ONCE_PER_RETRY currently have incorrect behaviour. They are not retrying in the case of failures without a checkpoint.

This PR adds the correct AT_MOST_ONCE_PER_RETRY behaviour as part of a new enum (StepSemanticsPerRetry) in order to prevent a breaking change to users of the current StepSemantics.AT_MOST_ONCE_PER_RETRY.

• Users can opt to use the new StepSemanticsPerRetry.AT_MOST_ONCE_PER_RETRY to get the correct AT_MOST_ONCE_PER_RETRY behaviour.
• The existing StepSemantics with incorrect AT_MOST_ONCE_PER_RETRY behaviour is still available.
• StepSemanticsPerRetry is null by default. So there will be no behaviour changes for users that haven't specified StepSemanticsPerRetry.
• StepSemantics is being marked as deprecated, and will be fully removed in the next version update.

Code Changes

• New StepSemanticsPerRetry.java.
• StepSemantics.java has been marked as deprecated.
• StepConfig.java
  • Added StepSemanticsPerRetry field/accessor/build.
  • Deprecated StepSemantics methods.
• StepOperation.java
  • Updated to work with new StepSemanticsPerRetry.
  • Now retries on StepInterruptedException only when StepSemanticsPerRetry == AT_MOST_ONCE_PER_RETRY.
• StepSemanticsIntegrationTest.java
  • Added tests for StepSemanticsPerRetry.
  • Updated the StepSemantics.AT_MOST_ONCE_PER_RETRY test to make clear that it is accepting incorrect behaviour, and this behaviour is being kept for backwards compatability.
• StepConfigTest.java added tests for StepSemanticsPerRetry.

Demo/Screenshots

Checklist

• I have filled out every section of the PR template
• I have thoroughly tested this change

Testing

Unit Tests

Have unit tests been written for these changes? YES

Integration Tests

Have integration tests been written for these changes? YES

Examples

Has a new example been added for the change? (if applicable) N/A

One more thing to consider