Add recovery and password settings flows

[natalian98]

Testing

docker-compose -f docker-compose.dev.yml up --build --force-recreate --remove-orphans

make npm-build build

export KRATOS_PUBLIC_URL="http://localhost:4433"
export HYDRA_ADMIN_URL="http://localhost:4445"
export BASE_URL="http://localhost:4455"
export PORT="4455"
export TRACING_ENABLED="false"
export LOG_LEVEL="debug"
export AUTHORIZATION_ENABLED="false"

go run . serve

Go to localhost:4455/ui/reset_email:

The link to reset password is also added to the login screen:

Enter a valid email. I use test@example.com because that's the only imported identity in kratos. Get the recovery code from mailslurper at localhost:4436.

Once a valid code is submitted, a kratos session is created. The recovery flow redirects to password change screen and starts a settings flow:

If you have an application that is a client of hydra, you will be automatically logged into it if opened in the same browser session as the completed recovery flow. If you start a new browser session you can verify that the credential was updated.

[natalian98]

There is a case that @edlerd is looking at: If you are logged in and have a kratos session, you should be able to change your password without the need of going through recovery, but rn going directly to localhost:4455/ui/reset_password redirects to http://localhost:4455/ui/ which doesn't exist.

[edlerd]

There is a case that @edlerd is looking at: If you are logged in and have a kratos session, you should be able to change your password without the need of going through recovery, but rn going directly to localhost:4455/ui/reset_password redirects to http://localhost:4455/ui/ which doesn't exist.

This has been handled.

[edlerd]

In case no text or an invalid email is entered, the POST api/kratos/self-service/recovery responds with the text content 400 Bad Request. As this is displayed to the user, it would be nice to have a better error message in this case.

[shipperizer]

couple of small commit message nudges:

• try to bundle the tests in 4c7ee6912718c77142fe6d78c751be89d45936d8 with the code if u can
• first wip commit needs to become a feat or fix

[shipperizer]

@natalian98 do a rebase and then it's mergeable