Add a Timeline Changelog under Logs for daily configuration changes

What:
Add a Timeline Changelog under Logs that presents a concise, technical, day-by-day record of configuration changes in a structured, markdown-like format.

Value:
Provides immediate visibility into what changed, when, and how, without digging through raw logs. This improves troubleshooting, change validation, team awareness, and operational accountability.

How it should work:
Introduce a new sub-item under Logs:

• Logs
• Timeline Changelog

Each day with changes generates an entry formatted like:

## 2026-04-20

* Host Pool: HostPoolX (WorkspaceY)
  * Auto-scale configuration updated
    * Base Host Pool Capacity: 1 → 3
    * Min Active Hosts: 1 → 2

* Desktop Image: Win11-Base
  * New version activated
    * Version: v1.2 → v1.3

* FSLogix Profile: FSLogix-Prod
  * Profile configuration updated
    * CCDLocation added
      * Previous: \\storage01\profiles
      * Current: \\storage01\profiles;\\storage02\profiles

* Scripted Actions
  * Assigned "Optimize-AVD" to HostPoolZ

Formatting principles (important):

• One section per day → ## YYYY-MM-DD
• Bullet-based structure
• Clear hierarchy:
  • Object → Change type → Before/After values
• Technical, concise wording (no narrative fluff)
• Only include days where changes occurred
• Order entries chronologically within the day

Scope of changes to track (examples):

• Host pool configuration (auto-scale, sizing, policies)
• Desktop image changes (versions, assignments)
• Scripted Action assignments or modifications
• FSLogix configuration updates (including CCDLocation changes)
• RDP profile changes
• Session limits
• Resource linking/unlinking
• RBAC changes (optional but valuable)

Optional enhancements:

• Include initiating user (who made the change)
• Filter by:
  • Workspace
  • Host Pool
  • Change type
• Export to CSV/JSON
• API access for integration with external reporting
• Clickable entries to jump to affected objects

Why this matters:
Today, understanding change history requires manually correlating logs or external tracking. A structured changelog makes it trivial to:

• Correlate incidents with recent changes
• Audit configuration drift
• Identify unexpected or undocumented changes
• Maintain shared awareness across teams

Summary:
This would turn scattered log data into a clean, structured, human-readable timeline—bringing version-control-style clarity to Nerdio configuration changes.