Refactor order payment process and enhance invoice details

- Updated `payOrder` method in `OrderControllerRefactor` to accept `orderNum` instead of `id` for better clarity and functionality.
- Implemented `findByOrderNum` method in `OrderRepository` to retrieve orders based on order number and customer ID.
- Enhanced `InvoiceDetailResource` to include VMware details and removed unnecessary fields.
- Added `service_plan_id` to `ProductResource` and updated the `Product` model to establish a relationship with `ServicePlan`.
- Created `ServicePlan` and `ServicePlanPlesk` models along with their respective controllers and migrations for managing hosting service plans.
- Updated API routes to include endpoints for managing service plans.
- Modified email templates to standardize support phone number across various customer communications.

app/Repositories/Api/Order/OrderRepositoryInterface.php

@@ -29,4 +29,9 @@ interface OrderRepositoryInterface extends BaseRepositoryInterface
      * Paginated order list for a customer, with optional filters.
      */
     public function getOrders(int $customerId, array $filters): LengthAwarePaginator;
+
+    /**
+     * Find an order by order_num, scoped to the owning customer.
+     */
+    public function findByOrderNum(string $orderNum, int $customerId): ?Order;
 }