refactor: Rename Property/PropertyType to CustomFieldValue/CustomField

Complete refactoring of resources, database tables, code references, tests, and documentation for improved naming consistency.

lib/membership/member.ex

@@ -7,7 +7,7 @@ defmodule Mv.Membership.Member do
   can have:
   - Personal information (name, email, phone, address)
   - Optional link to a User account (1:1 relationship)
-  - Dynamic custom properties via PropertyType system
+  - Dynamic custom field values via CustomField system
   - Full-text searchable profile
 
   ## Email Synchronization
@@ -16,7 +16,7 @@ defmodule Mv.Membership.Member do
   See `Mv.EmailSync` for details.
 
   ## Relationships
-  - `has_many :properties` - Dynamic custom fields
+  - `has_many :custom_field_values` - Dynamic custom fields
   - `has_one :user` - Optional authentication account link
 
   ## Validations
@@ -48,8 +48,8 @@ defmodule Mv.Membership.Member do
 
     create :create_member do
       primary? true
-      # Properties can be created along with member
-      argument :properties, {:array, :map}
+      # Custom field values can be created along with member
+      argument :custom_field_values, {:array, :map}
       # Allow user to be passed as argument for relationship management
       # user_id is NOT in accept list to prevent direct foreign key manipulation
       argument :user, :map, allow_nil?: true
@@ -70,7 +70,7 @@ defmodule Mv.Membership.Member do
         :postal_code
       ]
 
-      change manage_relationship(:properties, type: :create)
+      change manage_relationship(:custom_field_values, type: :create)
 
       # Manage the user relationship during member creation
       change manage_relationship(:user, :user,
@@ -95,8 +95,8 @@ defmodule Mv.Membership.Member do
       primary? true
       # Required because custom validation function cannot be done atomically
       require_atomic? false
-      # Properties can be updated or created along with member
-      argument :properties, {:array, :map}
+      # Custom field values can be updated or created along with member
+      argument :custom_field_values, {:array, :map}
       # Allow user to be passed as argument for relationship management
       # user_id is NOT in accept list to prevent direct foreign key manipulation
       argument :user, :map, allow_nil?: true
@@ -117,7 +117,7 @@ defmodule Mv.Membership.Member do
         :postal_code
       ]
 
-      change manage_relationship(:properties, on_match: :update, on_no_match: :create)
+      change manage_relationship(:custom_field_values, on_match: :update, on_no_match: :create)
 
       # Manage the user relationship during member update
       change manage_relationship(:user, :user,
@@ -349,7 +349,7 @@ defmodule Mv.Membership.Member do
   end
 
   relationships do
-    has_many :properties, Mv.Membership.Property
+    has_many :custom_field_values, Mv.Membership.CustomFieldValue
     # 1:1 relationship - Member can optionally have one User
     # This references the User's member_id attribute
     # The relationship is optional (allow_nil? true by default)