Small CAC refactoring in prep for CAC 2.0 and wizardless flow

[HarrisonHough]

TICKETID

Description

• This PR adds some minor changes which should add some extra flexibility and help us in CAC 2.0. Please share your feedback though and point out any potential floors in the updates. I will list some main changes and the reasoning below.

1. Added an extra return property to the CreateAvatar(AvatarProperties avatarProperties) method (made it return a tuple same as CreateAvatarFromTemplate.
Reasoning: To create an avatar from a photo with gender prediction enabled we need to also have the avatar properties, in particular we can get the gender of the predicted avatar which is required to load/update the avatar.

2. Removed gender from AvatarManager constructor
Reasoning: this makes AvatarManager easier to work with as you don't need to create a new one each time you change genders. Also CreateAvatar() function is passed avartarProperties (which can optionally have gender predefined) and CreateAvatarFromTemplate gets the gender from Template data. The only thing that may be useful in future is to add a separate "SetGender" function but at the moment I don't really see a use for it.

3. Removed partner parameter from CreateAvatarFromTemplate() function.
Reasoning: Why would anybody ever want to pass a "partner" value that is not the same as in their CoreSettings ? Doing so would probably break API's anyways (due to non matching subdomain and API key

How to Test

• Mainly just test that current CAC sample still works (and it should)

Checklist

• Tests written or updated for the changes.
• Documentation is updated.
• Changelog is updated.

[rYuuk]

🟢 Looks good