feat: complete PDF/UA Investor Statement verification and fix global …

[OLAMIGHTY010]

Pull Request: PDF/UA Investor Statement Verification & Global Syntax Fixes

Resolves: #416

Description

This PR addresses several UI/UX and compliance goals, primarily focusing on completing the PDF/UA verification for Investor Statements. It also introduces various global syntax fixes, layout adjustments to the Payout Schedule, and test coverage improvements to maintain code quality.

Key Changes

1. Investor Statement (PDF/UA Compliance)

• Completed PDF/UA Verification: Fixed accessibility and structural constraints within InvestorStatement.tsx and its test suite to align with PDF/UA compliance standards.
• Test Coverage: Explicitly added InvestorStatement.tsx and usePrintStatement.ts to the coverage thresholds in vite.config.ts to ensure ongoing validation.

2. Payout Schedule Enhancements

• UI Refinements: Improved the visual hierarchy and layout of the Gantt chart and table views in PayoutSchedule.tsx.
• Status Legend & Pattern Keys: Updated the layout of the status legend and Gantt pattern keys for better readability and accessibility contrast.

3. Global Syntax Fixes & Code Cleanup

• Component Fixes: Resolved syntax warnings and cleaned up unused imports/variables across multiple components:
  • CommandPalette.tsx
  • KycSelfieCapture.tsx
  • OnChainStatusBadge.tsx
  • Tabs.tsx
  • DistributionDashboard.tsx
  • OfferingDetail.tsx
• Test Suite Updates: Updated TwoFactorSetup.test.tsx to align with recent component changes.
• Dependencies: Cleaned up package.json and synchronized package-lock.json.

Testing Instructions

1. Run npm run test to verify that InvestorStatement.test.tsx passes and coverage requirements in vite.config.ts are met.
2. Navigate to the Payout Schedule screen to ensure the Gantt Chart, Table Fallback, and Status Legend render correctly across different viewport sizes.
3. Verify that the global UI components (Command Palette, Tabs, etc.) behave properly with no console warnings.

Checklist

• Tested locally
• All automated checks and tests pass
• Code meets accessibility (WCAG / PDF/UA) standards
• Test coverage maintained/improved