Add services override for forcing new password

[jiw-mh]

Description of changes

Adds a way to override/extend the confirmSignIn call done when the new password dialog is done.

Description of how you validated changes

Checklist

• Have read the Pull Request Guidelines
• PR description included
• yarn test passes and tests are updated/added
• PR title and commit messages follow conventional commit syntax
• If this change should result in a version bump, changeset added (This can be done after creating the PR.) This does not apply to changes made to docs, e2e, examples, or other private packages.

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

[changeset-bot]

🦋 Changeset detected

Latest commit: 3c0b793

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 13 packages

Name	Type
@aws-amplify/ui	Minor
@aws-amplify/ui-react-core-notifications	Patch
@aws-amplify/ui-react-core	Patch
@aws-amplify/ui-react-liveness	Patch
@aws-amplify/ui-react-native	Patch
@aws-amplify/ui-react-notifications	Patch
@aws-amplify/ui-react-storage	Patch
@aws-amplify/ui-react	Patch
@aws-amplify/ui-svelte	Patch
@aws-amplify/ui-vue	Patch
@aws-amplify/ui-angular	Patch
@aws-amplify/ui-react-geo	Patch
@aws-amplify/ui-test-utils	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[bobbor]

hey @jiw-mh

thanks for raising the PR. contributions are always very welcome.

the code looks good, I'd just like to see a test added, for the signIn-actor, so that a handleForceChangePassword service function provided is actually called, with the correct input.

[jiw-mh]

@bobbor I rebased the PR and found a problem that would stop the tests from passing. I tried today to add a test, but since the current tests are skipped

amplify-ui/packages/ui/src/machines/authenticator/actors/__tests__/signIn.test.ts

Line 337 in 27c8299

it.skip('transitions to forceNewPassword when challengeName is NEW_PASSWORD_REQUIRED', async () => {

and trying to re-enable them has been fruitless so far, as I am not familiar with the changes and it seems more than a little is broken. It would be nice if there was advice/help on how to add a test around that.