Add authentication middleware

[daniel-orlov]

Is your feature request related to a problem? Please describe.
Currently, our server lacks a standardized and secure authentication mechanism. We need a robust solution to authenticate users based on their username and password, ensuring that only authorized users can access protected resources and perform sensitive operations. Implementing username-password authentication as a middleware will help us improve the overall security posture of our application.

Describe the solution you'd like
I propose the addition of an authentication middleware based on username-password authentication to our server. This middleware should handle the following key functionalities:

1. User Registration: Provide an endpoint to allow new users to create an account with a unique username and a strong, securely hashed password.
2. User Login: Implement an endpoint that accepts a username and password and verifies them against the stored credentials. Successful authentication should generate a session token or JSON Web Token (JWT) for subsequent authenticated requests.
3. Password Management: Include mechanisms for users to reset their passwords securely in case they forget or need to change them.
4. Password Encryption: Ensure that user passwords are securely hashed and encrypted using a strong cryptographic algorithm to prevent unauthorized access to sensitive information.
5. Session Management: Maintain authenticated user sessions securely to provide seamless access to protected resources without repeated logins.

Describe alternatives you've considered
Currently, we might be using basic authentication or no authentication at all. However, implementing a dedicated authentication middleware with username-password authentication will significantly enhance the security of our application and provide a more user-friendly login experience.

Additional context
The addition of username-password authentication middleware will strengthen our server's security and protect user accounts from unauthorized access. Any specific preferences or requirements, such as the choice of encryption algorithms or session management approach, should be discussed in more detail.

This is related to #3