un opérateur peut bloquer un compte

[LeSim]

No description provided.

[what-the-diff]

PR Summary

• Addition of 'blocked_at' and 'blocked_reason' attributes to users
  This modification has added new data fields named blocked_at and blocked_reason to the users' database table. This will let us track when the user got blocked and why they were blocked.
• Database migration for user changes
  A necessary update script has been generated to include these changes to the existing database. The file is named 20230718113720_add_blocked_at_block_reasonto_user.rb.
• Updates to User model
  The User data model has been extended with these two new attributes: blocked_at and blocked_reason. This enables our system to recognize and handle these new pieces of user information.
• Added a method to check the user's active status
  A method called active_for_authentication? was added to the User model. It will determine if a user's account is active or blocked based on the new attributes.
• Database schema updated
  The general blueprint of our database, the db/schema.rb file, is updated with these changes. It now illustrates the additions of blocked_at and blocked_reason.
• New scenario for user sign-in testing
  Added a new test case in sign_up_spec.rb to check that a blocked, yet confirmed, user cannot sign into the system. This will ensure that our block functionality works as intended.