feat: Implement workspace-level cycle analytics

[pqhung3007]

This commit adds comprehensive cycle analytics functionality for free users, following the same structure and UI patterns as work items analytics.

Backend changes:

• Added cycle analytics endpoints to workspace analytics API
• Implemented get_cycle_stats() for top-level metrics (total, current, upcoming, completed cycles)
• Implemented get_cycles_table_stats() for detailed cycle table data with work item counts
• Implemented cycle_completion_chart() for bar chart showing completion percentage by cycle status
• Added support for project filtering across all cycle analytics endpoints

Frontend changes:

• Updated analytics types to include "cycles" in TAnalyticsTabsBase and TAnalyticsGraphsBase
• Added CycleInsightColumns interface for cycle table data
• Added cycle insight fields to ANALYTICS_INSIGHTS_FIELDS constants
• Created new cycle analytics components:
  • root.tsx - Main cycle analytics container
  • cycle-completion-chart.tsx - Bar chart showing completion % by cycle status with tooltips
  • cycles-insight-table.tsx - Searchable, exportable table with cycle details
• Added "cycles" tab to analytics configuration

Features:

• Top section displays 4 key metrics: Total, Current, Upcoming, and Completed cycles
• Bar chart visualizes completion percentage for each active cycle, color-coded by status:
  • Current cycles: Orange
  • Upcoming cycles: Blue
  • Completed cycles: Green
  • Draft cycles: Gray
• Interactive tooltips on hover show cycle name, completion %, dates, and work item breakdown
• Table section includes cycle name, lead, project, dates, and completion percentage
• Full search and CSV export functionality
• Project filter dropdown to filter analytics by specific projects

This implementation provides free users with powerful cycle analytics capabilities previously only available in paid tiers.

Description

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Improvement (change that would cause existing functionality to not work as expected)
• Code refactoring
• Performance improvements
• Documentation update

Screenshots and Media (if applicable)

Test Scenarios

References