feat(predictions): Add support for a no light freshness challenge

[vincetran]

• PR title and description conform to Pull Request guidelines.

Issue #, if available: N/A

Description of changes:
This adds support for a no-light challenge to the Prediction plugin's Face LIveness feature and adds telemetry tracking as requested by the Rekognition team. There's no API change to the core plugin API and additive changes to the FaceLivenessSessionInformation data class that's used as part of the API.

Notable callouts:

• FaceLivenessSessionInformation
  • Changed the String challenge parameter to be nullable. This is required to allow backward compatibility with the existing Liveness UI component library.
  • Added a new parameter challengeVersions to replace the previous challenge which takes in a List<Challenge>. These Challenges represent both the challenge name and the version for that challenge.
  • Added a new parameter preCheckViewEnabled which signifies if the default "Start View" was enabled. Used for telemetry.
  • Added a new parameter attemptCount which signifies how many times the user attempted to perform the liveness check. Used for telemetry.
• Added a new supported challenge called FaceMovementChallenge that will live alongside the existing supported FaceMovementAndLightChallenge
• Updated the websocket endpoint generation to use a Uri.Builder() for code cleanliness
• Added support for a new web socket event called ChallengeType which is used for determining what type of challenge is requested from the backend to render to the user.

How did you test these changes?

• Updated and added unit tests for the new ChallengeType event
• Tested with a corresponding Amplify UI change that accepts the new challenge type and renders it
• Tested with the existing version of Amplify UI to ensure backwards compatibility

Documentation update required?

• No
• Yes (Please include a PR link for the documentation update)

General Checklist

• Added Unit Tests
• Added Integration Tests
• Security oriented best practices and standards are followed (e.g. using input sanitization, principle of least privilege, etc)

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

[tylerjroach]

Can you add some tests on the new UrlBuilder being used on the websocket?