feat: add aggregate boundary validation (v0.7.0)

Implement DDD aggregate boundary validation to detect and prevent direct
entity references across aggregate boundaries.

Features:
- Detect direct entity imports between aggregates
- Allow only ID or Value Object references
- Support multiple folder structures (domain/aggregates/*, domain/*, domain/entities/*)
- Filter allowed imports (value-objects, events, repositories, services)
- Critical severity level for violations
- 41 comprehensive tests with 92.55% coverage
- CLI output with detailed suggestions
- Examples of good and bad patterns

Breaking changes: None
Backwards compatible: Yes

packages/guardian/examples/aggregate-boundary/good/Order-IdReference.ts

@@ -0,0 +1,40 @@
+/**
+ * ✅ GOOD EXAMPLE: Reference by ID
+ *
+ * Best Practice: Order aggregate references other aggregates only by their IDs
+ *
+ * Benefits:
+ * 1. Loose coupling between aggregates
+ * 2. Each aggregate can be modified independently
+ * 3. Follows DDD aggregate boundary principles
+ * 4. Clear separation of concerns
+ */
+
+import { UserId } from "../user/value-objects/UserId"
+import { ProductId } from "../product/value-objects/ProductId"
+
+export class Order {
+    private id: string
+    private userId: UserId
+    private productId: ProductId
+    private quantity: number
+
+    constructor(id: string, userId: UserId, productId: ProductId, quantity: number) {
+        this.id = id
+        this.userId = userId
+        this.productId = productId
+        this.quantity = quantity
+    }
+
+    getUserId(): UserId {
+        return this.userId
+    }
+
+    getProductId(): ProductId {
+        return this.productId
+    }
+
+    getQuantity(): number {
+        return this.quantity
+    }
+}