Added new models and schemas for gender, address type, and shipping type.

- ✨ **Feature**: Introduced Gender, AddressType, and ShippingType enums
- 🗑️ **Chore**: Removed obsolete schemas and service files from return feature
- 🛠️ **Refactor**: Updated index files to export new models

.github/review-instructions.md

@@ -55,7 +55,7 @@ High-priority issues that must be addressed immediately due to their potential t
 
 ### 1. High Priority: [Issue Title]
 
-#### 🎯 Issue
+#### 🚨 Issue
 
 Describe the issue clearly, including links to specific files and lines (e.g., file.js#L10). Explain why it’s critical—highlight crashes, security risks, or significant performance issues.
 
@@ -65,9 +65,16 @@ Provide specific steps or alternative approaches to resolve the issue.
 
 #### ✨ Code Example
 
+**Current**: [file](file.js#L10) Problematic code with path to the file and line of the code
+
 ```typescript
-// Before: Problematic code
-// After: Improved version
+// Code...
+```
+
+**Improvement**: Improved version
+
+```typescript
+// Code...
 ```
 
 #### 📚 Relevant Documentation
@@ -92,9 +99,16 @@ Offer concrete steps or alternative approaches to mitigate the issue.
 
 #### ✨ Code Example
 
+**Current**: [file](file.js#L10) Problematic code with path to the file and line of the code
+
 ```typescript
-// Before: Problematic code
-// After: Improved version
+// Code...
+```
+
+**Improvement**: Improved version
+
+```typescript
+// Code...
 ```
 
 #### 📚 Relevant Documentation
@@ -119,9 +133,16 @@ Provide suggestions or alternative implementations to mitigate the issue.
 
 #### ✨ Code Example
 
+**Current**: [file](file.js#L10) Problematic code with path to the file and line of the code
+
 ```typescript
-// Before: Problematic code
-// After: Improved version
+// Code...
+```
+
+**Improvement**: Improved version
+
+```typescript
+// Code...
 ```
 
 #### 📚 Relevant Documentation
@@ -130,9 +151,20 @@ Include relevant resources for more information.
 
 ---
 
+## 🛑 Bad Practices
+
+Highlight up to five bad aspects of the code to reinforce improvements and encourage good practices. Use different funny emoji at the beginning of each bad practice.
+
+- Emoji **Bad Practice 1**:  
+   Describe a specific weakness (e.g., clear code structure) with an example reference (e.g., file.js#L20). Explain why it’s bad.
+- Emoji **Bad Practice 2**:  
+   Outline another negative feature (e.g., effective error handling) with a snippet reference.
+
+---
+
 ## ✅ Good Practices
 
-Highlight one up to five positive aspects of the code to reinforce well-implemented patterns and encourage good practices. Use different funny emoji at the beginning of each good practice.
+Highlight up to five positive aspects of the code to reinforce well-implemented patterns and encourage good practices. Use different funny emoji at the beginning of each good practice.
 
 - Emoji **Good Practice 1**:  
    Describe a specific strength (e.g., clear code structure) with an example reference (e.g., file.js#L20). Explain why it’s commendable.