Add address management and user details retrieval functionality

[NourAlPha]

This pull request introduces several enhancements and fixes to the authentication module, including improved validation, new DTOs for user updates and details, and expanded functionality in the User and Address models. The changes also include updates to the pom.xml dependencies and the addition of new service methods and exception handling.

Dependency Updates

• Updated podzilla-utils-lib dependency to version v1.1.6 in pom.xml.
• Added spring-boot-starter-validation dependency to enable validation annotations.

Validation Enhancements

• Added @Valid annotations to request bodies in AuthenticationController methods (login and registerUser) for automatic validation. [1] [2]
• Introduced validation annotations (@NotBlank, @Email) in LoginRequest and SignupRequest DTOs to enforce field constraints. [1] [2]
• Implemented handleMethodArgumentNotValid in GlobalExceptionHandler to provide detailed error messages for validation failures.

User and Address Model Enhancements

• Added mobileNumber and a one-to-one relationship with the Address entity to the User model.
• Created a new Address entity with fields for street, city, state, country, and postal code, linked to the User model.
• Added AddressRepository for database operations on the Address entity.

New DTOs and Controller Features

• Introduced UpdateRequest and UserDetailsRequest DTOs for user profile updates and fetching user details. [1] [2]
• Enhanced UserController with a new getUserDetails endpoint and updated updateProfile to use UpdateRequest.

Service and Utility Updates

• Refactored AuthenticationService to include getCurrentUserDetails and updated header methods to include X-User-Id. [1] [2]
• Updated AdminService to include id in CustomUserDetails.
• Added validation for unique mobile numbers in registerAccount in AuthenticationService.