feat: add analytics tools for flow metrics, WIP analysis, and aging reports

[viamus]

Description

Add analytics tools to transform the MCP server from a data access layer into an analytical and management tool. These tools enable answering strategic questions about delivery performance, bottlenecks, team
workload, and work health.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)

Related Issues

Closes #(analytics-feature)

Changes Made

• Add get_flow_metrics tool - calculates Lead Time, Cycle Time, and Throughput with statistical analysis (average, median, percentiles 85/95, std dev)
• Add compare_flow_metrics tool - compares metrics between two periods to identify delivery trends
• Add get_wip_analysis tool - analyzes Work in Progress by state, area, and person with insights
• Add get_bottlenecks tool - identifies workflow bottlenecks with severity scores and actionable recommendations
• Add get_team_workload tool - analyzes workload distribution across team members (overloaded/balanced/has capacity)
• Add get_aging_report tool - reports aging work items with urgency classification (Critical/High/Medium/Low) and specific recommendations
• Add FlowMetricsDto.cs with DTOs for flow metrics, statistics, and throughput periods
• Add WipAnalysisDto.cs with DTOs for WIP analysis, bottlenecks, and aging reports
• Add AnalyticsTools.cs with all 6 MCP tool implementations
• Add comprehensive unit tests for all new DTOs (22 new tests)
• Update README with analytics tools documentation, usage examples, and API reference
• Bump version to 1.2.0

Testing

• I have tested these changes locally
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Test Results: 267 tests passing (22 new analytics tests added)

Checklist

• My code follows the project's coding style
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I have updated the documentation accordingly

Screenshots (if applicable)

N/A - Backend MCP tools

Additional Notes

New Analytics Capabilities

Question	Tool
"Are we delivering faster or slower?"	compare_flow_metrics
"Where is work piling up?"	get_bottlenecks
"Who is overloaded?"	get_team_workload
"What needs attention now?"	get_aging_report
"What's our average delivery time?"	get_flow_metrics
"How many items did we complete?"	get_wip_analysis

Key Metrics Provided

• Lead Time: Creation → Completion (total delivery time)
• Cycle Time: Started → Completion (active work time)
• Throughput: Items completed per period
• WIP Distribution: By state, area, person, type
• Aging Analysis: Urgency scoring based on priority, time, and state

Files Added

src/Viamus.Azure.Devops.Mcp.Server/
├── Models/
│ ├── FlowMetricsDto.cs (139 lines)
│ └── WipAnalysisDto.cs (254 lines)
└── Tools/
└── AnalyticsTools.cs (1,200+ lines)

tests/Viamus.Azure.Devops.Mcp.Server.Tests/Models/
├── FlowMetricsDtoTests.cs (180 lines)
└── WipAnalysisDtoTests.cs (280 lines)