fix(ui): improve progress accessibility

[wyf027]

Summary

• add determinate role="progressbar" semantics to Progress
• keep aria-valuenow, aria-valuemin, aria-valuemax, and aria-valuetext aligned with the clamped percent
• support distinct progress names via aria-label / aria-labelledby
• add Progress accessibility tests and update the VitePress API docs

Why

The existing Progress component exposed the visual percentage but did not expose range semantics to assistive technology. Ant Design and Element Plus both treat Progress as a first-class feedback component, and MDN documents progressbar as the ARIA role for determinate long-running task progress:

• https://ant.design/components/progress/
• https://element-plus.org/en-US/component/progress
• https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Reference/Roles/progressbar_role

Validation

• npm ci
• npx prettier --write packages/ui/src/components/data/Progress/Progress.tsx packages/ui/src/components/data/Progress/Progress.test.tsx docs/components/progress.md
• npm run lint:ui
• npm run typecheck:ui
• npm run test:ui (24 files, 73 tests)
• npm run build:ui
• npm run build
• bash /Users/wuyangfan/.cursor/skills/git-commit/scripts/run-audit.sh (OVERALL_EXIT=0)

Existing non-blocking warnings observed:

• npm ci reports 7 existing audit findings.
• Vitest reports existing Vite/Babel deprecation warnings.
• UI/docs builds report existing Browserslist/chunk-size warnings.

[ecc-tools]

ECC bundle files are already tracked in this repository. Skipping generation of another bundle PR.