Refactor mentor and user schemas to centralize personal data management

- Updated `seed_mentor_user.rs` to include additional fields in the `app_users` creation and removed redundant fields from `app_mentors`.
- Modified `seed_users.rs` to initialize new user fields including legal name, domicile, and professional links.
- Adjusted `mentors_dto.rs` to remove personal data fields from `MentorDetailWithUserDto` and `MentorDetailResponseDto`, now sourced from `UsersSchema`.
- Updated `mentors_repository.rs` to search for user data through `user_id` instead of mentor fields.
- Refined `mentors_schema.rs` to remove personal data fields, now managed in `UsersSchema`.
- Enhanced `mentors_service.rs` to populate mentor responses with user data from `UsersSchema`.
- Removed identity document URL and related fields from various DTOs and schemas across the codebase.
- Updated tests to reflect the removal of identity document URL and ensure compatibility with the new schema structure.

tests/src/lib.rs

@@ -31,7 +31,6 @@ pub fn create_test_user(
 		gender: None,
 		birthdate: None,
 		domicile: None,
-		identity_document_url: None,
 		bio: None,
 		last_education: None,
 		linkedin_url: None,

tests/src/mock_test.rs

@@ -161,7 +161,6 @@ pub async fn seed_users_for_test(
 			gender: None,
 			birthdate: None,
 			domicile: None,
-			identity_document_url: None,
 			bio: None,
 			last_education: None,
 			linkedin_url: None,