HIVE360 Enterprise Domain - 30-Day Service Control Usage Fix

Problem found:
The previous module usage code often selected created_at before the real business activity
date. This made the 30-day figures inaccurate for imported/created records and several
enterprise modules.

Fix:
- Uses an inclusive calendar window (today plus previous 29 calendar days).
- Uses business activity date first.
- Filters last_activity to the same requested window.
- Treats master/configuration data (employees, products, suppliers, fixed assets) as current
  configuration counts rather than pretending those totals are 30-day transaction activity.
- Returns date_field/from/to for every time-window metric for easier verification.

Examples of corrected activity fields:
orders -> ordered_at
stock receiving -> received_date
stock issuing -> issued_at
purchase requisition -> request_date
expenses -> payed_date
deposits -> deposited_date
GL journals -> journal_date / posted_at
HR attendance -> attendance_date
payroll payments -> payment_date
asset maintenance -> maintenance_date
asset transfers -> transfer_date
document approvals -> acted_at / requested_at
production -> production_date

Replace:
application/models/Crm_integration_model.php

The controller/routes are included unchanged for deployment convenience.

No SQL migration is required.

After upload, click Sync Module Usage again. The endpoint response also includes
window_from/window_to and each metric's selected date_field so you can verify the exact period.
