feat(phase2): add @attr declarations for vendor freight, place operational, and service-area scoping fields

[TLemmAI]

Summary

Adds missing Ember Data @attr declarations on three existing models to support Phase 2 of the upstream fleetbase/core-api multi-tenant / settings work.

Without these, the Ember frontend in fleetbase/fleetops ignores assignments to the new fields, omits them from serialized payloads on save, and drops them from deserialized responses on load — so freshly-added UI form fields don't round-trip through Ember Data.

Vendor (9 new attrs — freight / carrier fields)

• scac_code (string)
• mc_number (string)
• dot_number (string)
• insurance_expiry (date)
• insurance_amount (number)
• payment_terms_days (number)
• default_payment_method (string)
• carrier_type (string)
• is_preferred (boolean)

Place (5 new attrs — operational / contact fields)

• location_type (string)
• appointment_required (boolean)
• contact_name (string)
• contact_phone (string)
• contact_email (string)

ServiceArea (2 new attrs — non-polygon geographic scoping)

• states_list (raw — array of state codes)
• zip_ranges (raw — array of {start, end} range objects)

Backend context

The backend columns were added in corresponding migrations in the upstream fleetops server (carrier freight, place operational, service-area state/zip scoping). This change is additive; existing attrs are untouched.

Test plan

• Import-from-fleetbase console app pulls this version via pnpm
• Vendor create/edit form round-trips all 9 new fields
• Place create/edit form round-trips all 5 new fields + preserves meta for operating_hours / dock_info / special_instructions
• ServiceArea create/edit form round-trips states_list + zip_ranges while leaving polygon border untouched

[TLemmAI]

#48 merged