Refactor user registration workflow

[vladyslavyarets]

Description

Every user in our application should be an owner of some apartment. Once apartment created it should already have a list of ownerships (see ticket #478). Important user information as full name should be filled by cooperation admin during apartment creation. In this way during registration process user should not change it. There 2 types of owners can be created. Person and New workflow depends with other steps:

• Cooperation admin crates apartment where filled users information. User's information with data saves into Database
• After this by owner request cooperation admin can create invitation for user by concrete email. During this process registration token generates and sends to user with email

If user is a person:

• user set the following fields: registration token, email, password and phone number.

If user is a legal_state:

• user set all fields for a person and his full name.

• After user confirm registration and there is no exception situations user record into Database updates and user becomes active

Tasks:

1. Rewrite OpenApi specification due to new model. Example of required payload present below:

For person:

{
  "user_id": 4
  "registration_token": "7b3a32f0-1326-11ed-b2e2-b51ca8f90a82",
  "email": "test@gmail.com",
  "password": "Passw0rd",
  "phone_number": 380501112233
}

For legal_state user:

{
  "user_id": 4
  "registration_token": "7b3a32f0-1326-11ed-b2e2-b51ca8f90a82",
  "email": "test@gmail.com",
  "password": "Passw0rd",
  "phone_number": 380501112233
}

2. Rewrite service layer due to new logic.

3. Optimize user' contact information storage in the database

4. Rewrite api tests due to new logic

[vladyslavyarets]

Epic was merged with task #478