Update API documentation by removing obsolete customer-related fields and updating example values

- Removed references to customer assignment fields such as has_customer, owner_customer_id, and customer_id from Swagger documentation to streamline API clarity.
- Updated example values for password and username in the documentation to reflect current standards.
- Enhanced overall documentation consistency by eliminating outdated parameters and ensuring accurate representation of the API structure.

cmd/web/docs/swagger.yaml

@@ -114,8 +114,6 @@ definitions:
         type: string
       name:
         type: string
-      owner_customer_id:
-        type: string
       phone:
         type: string
       registration_number:
@@ -156,8 +154,6 @@ definitions:
           format: int64
           type: integer
         type: object
-      companies_with_customer:
-        type: integer
       top_categories:
         items:
           $ref: '#/definitions/company.CategoryCount'
@@ -274,9 +270,6 @@ definitions:
         description: Contact information
       currency:
         type: string
-      customer_id:
-        description: Customer assignment (for login credentials)
-        type: string
       description:
         type: string
       email:
@@ -866,11 +859,11 @@ definitions:
     properties:
       password:
         description: User password
-        example: SecurePass123!
+        example: Nima.1998
         type: string
       username:
         description: Username or email address
-        example: johnsmith
+        example: nakhostin
         type: string
     type: object
   user.RefreshTokenForm:
@@ -1052,10 +1045,6 @@ paths:
         in: query
         name: is_compliant
         type: boolean
-      - description: Filter by customer assignment status
-        in: query
-        name: has_customer
-        type: boolean
       - description: Filter by CPV codes
         in: query
         name: cpv_codes