v5.0.3: Fix issue with FrontendStateEnum and StateEnum for campaign notifications

[giou-k]

Summary

Issue 1:

And the second issue was that FrontendState is not being used properly by the java sdk. To fix this we introduced CampaignStateNotification in the respective .java obejcts.

In more detail see:

• Fix for FrontendState
  Because the link doesn't work, please see src/main/java/one/talon/model/CampaignEditedNotification.java

public class CampaignEditedNotification {
  public static final String SERIALIZED_NAME_CAMPAIGN = "campaign";
  @SerializedName(SERIALIZED_NAME_CAMPAIGN)
  private CampaignStateNotification campaign;

and then
CampaignStateNotification.java -> FrontendStateEnum

Explanation: Above we see that the CampaignEditedNotification encapsulates CampaignStateNotification, which encapsulates FrontendStateEnum.

Issue 2:

This PR includes (because of the generate process) another fix that is worth mentioning:

The initial issue that was reported by the TAM is that we are missing the extra 5 enums while we get a notificaiton on campaign state changed. This was hacky fixed at 5.0.2.

At 5.0.3 we introduce CampaignForNotification.javafor campaign state changed to fix the above mentioned issue.

In more detail see:

• Fix for StateEnum
  Because the link doesn't work, please see src/main/java/one/talon/model/CampaignForNotification.java line 79 (StateEnum)

The equivalent swagger change in talon-service can be found here

[merent1]

[sc-26314]

[shortcut-integration]

This pull request has been linked to Shortcut Story #26314: Fix issue with FrontendState in TalonJavaSDK repo.