feat: ESPI 4.0 Schema Compliance - Phase 26: Meter Complete Implementation

Implements full ESPI 4.0 compliance for Meter resource per customer.xsd.

Changes:
- Extracted shared embeddables to domain/customer/common/:
  * ElectronicAddress (customer.xsd lines 886-936)
  * StreetAddress (customer.xsd lines 1285-1320)
  * TelephoneNumber (customer.xsd lines 1428-1478)
  * MeterMultiplier (customer.xsd MeterMultiplier type)
- MeterEntity: Added meterMultipliers @ElementCollection
- MeterDto: Added 19 XSD-compliant fields including meterMultipliers
- MeterMultiplierDto: New DTO for meter multiplier collection
- MeterMapper: MapStruct mapper with UUID v5 generation
- MeterService: Simplified to 6 CRUD methods (ESPI 4.0 pattern)
- MeterRepository: Removed 11 non-ID query methods
- Flyway V3: Added meter_multipliers collection table
- TestDataBuilders: Added createValidMeter() helper
- Tests: 16 unit tests + 18 integration tests (MySQL/PostgreSQL)
- BigDecimal assertions: Use isEqualByComparingTo() for cross-platform precision
- CLAUDE.md: Added file modification best practices (NEVER use sed/awk)

Updated entities to use extracted embeddables:
- Organisation, Asset, Location, CustomerEntity, CustomerAccountEntity,
  CustomerAgreementEntity, EndDeviceEntity, OrganisationRole,
  ServiceLocationEntity and all related mappers and tests

All 736 tests passing.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: dfcoffin

CLAUDE.md

@@ -237,6 +237,40 @@ ESPI uses Atom XML feeds for data exchange. Key patterns:
 
 ### Common Development Patterns
 
+#### File Modification Best Practices
+**CRITICAL: Always use the Edit tool with visible diffs instead of sed/awk for file modifications**
+
+- **NEVER use sed, awk, or bash text manipulation** for modifying source code or test files
+- **ALWAYS use the Edit tool** which shows explicit diffs for review
+- **Benefits of Edit tool**:
+  - Changes are visible and reviewable before execution
+  - Prevents cascading errors from bulk updates
+  - Easy to verify correctness with explicit old_string → new_string diff
+  - Catches errors immediately rather than discovering them during compilation
+
+- **When multiple files need the same change**:
+  - Use multiple Edit tool calls (one per file) in a single message
+  - Show exactly what's changing in each file
+  - Do NOT use sed/awk loops even if it seems more efficient
+
+- **Exception**: Only use bash text tools (grep, find) for **searching/analysis**, never for modifications
+
+**Example - WRONG approach:**
+```bash
+# DON'T DO THIS - sed makes changes invisibly
+sed -i '' 's/OldClass/NewClass/g' src/**/*.java
+```
+
+**Example - CORRECT approach:**
+```
+# DO THIS - Use Edit tool with explicit diffs
+Edit tool call showing:
+old_string: "import com.example.OldClass;"
+new_string: "import com.example.NewClass;"
+```
+
+This practice prevents issues like missing imports, broken references, and compilation errors that are difficult to track down.
+
 #### Adding New ESPI Entity
 1. Create entity in `openespi-common/src/main/java/org/greenbuttonalliance/espi/common/domain/usage/` (or `/customer/`)
 2. Extend `IdentifiedObject` base class