feat(users): Decision manager flow changes for SSO

[ThisIsMani]

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

This PR adds SSO flows in login decision flows. Currently they are disabled as we have no APIs for SSO and will be enabled in upcoming PRs which adds SSO APIs.

Additional Changes

• This PR modifies the API contract
• This PR modifies the database schema
• This PR modifies application configuration/environment variables

Motivation and Context

Closes #4992.

How did you test it?

• There should be no changes in any of the flows.
• SPT changes can be tested as follows:

  1. Generate SPT using any of the token only APIs (I am using Sign in)

     curl --location 'http://localhost:8080/user/v2/signin?token_only=true' \
     --header 'Content-Type: application/json' \
     --data-raw '{
         "email": "email",
         "password": "password"
     }'
     

     {
         "token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjoiZTY4YzFmZTQtODRiMC00Y2NjLWI4NGYtN2VjYmVkNjg5Y2Q5IiwicHVycG9zZSI6InRvdHAiLCJvcmlnaW4iOiJzaWduX2luIiwicGF0aCI6W10sImV4cCI6MTcxODg3MzYyN30.HK_0mcCyvbFwh-nma48Pbeh2kdkO7s3FsVOtIc6UF9w",
         "token_type": "totp"
     }
     

  2. Complete the next step

     curl --location 'http://localhost:8080/user/2fa/terminate?skip_two_factor_auth=true' \
     --header 'Authorization: SPT with Purpose as `totp`' \
     

     {
         "token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ1c2VyX2lkIjoiMzBkOGVkYTEtOWM2ZC00MjgwLTg3MDgtN2MwMjBjY2U1ZmNkIiwicHVycG9zZSI6ImFjY2VwdF9pbnZpdGF0aW9uX2Zyb21fZW1haWwiLCJvcmlnaW4iOiJhY2NlcHRfaW52aXRhdGlvbl9mcm9tX2VtYWlsIiwicGF0aCI6WyJ0b3RwIl0sImV4cCI6MTcxODg3OTQ3OH0.tLsVZ-kYbaxaXaq3Jn4-kJ0ghswonTCjbclUrWZLeoc",
         "token_type": "accept_invitation_from_email"
     }
     

     The above token when decoded (using this), it should have the path field with the step that has been completed. And the SPT body will look something like this:

     {
       "user_id": "30d8eda1-9c6d-4280-8708-7c020cce5fcd",
       "purpose": "accept_invitation_from_email",
       "origin": "accept_invitation_from_email",
       "path": [
         "totp"
       ],
       "exp": 1718879478
     }
     

Checklist

• I formatted the code cargo +nightly fmt --all
• I addressed lints thrown by cargo clippy
• I reviewed the submitted code
• I added unit tests for my changes where possible

[apoorvdixit88]

LGTM, we can get this merged to use new purposes in auth select