Add accessible 'Why this API?' rationale on ApiCard

[greatest0fallt1me]

Description

This is a UI/UX issue for the GrantFox campaign. This is a UI/UX issue for the GrantFox campaign. Surface why an API was recommended.

Requirements and Context

• Implement per the description
• Add focused tests for the change
• Document any API/visible changes
• Adhere to repo's lint and code style
• Must be secure, tested, and documented
• Should be efficient and easy to review

Suggested Execution

1. Fork the repo and create a branch

   git checkout -b task/why-api

2. Implement changes
   • src/components/ApiCard.tsx
   • src/components/WhyApi.tsx (new)
3. Test and commit
   • Run the repo's standard test suite and lint
   • Cover edge cases; include output in the PR

Example commit message

feat: why this API rationale

Acceptance Criteria

• Implementation matches the description
• Tests added and passing
• Code review approved
• Docs updated

Guidelines

• Responsive across all breakpoints
• WCAG 2.1 AA accessibility
• Design-token + dark-mode consistency
• Clear documentation and inline comments
• Timeframe: 96 hours

[gloskull]

Hi, I’d love to work on this issue. I have 4 years of experience across backend, frontend, full-stack, and smart contract development. I understand the task clearly and can deliver a clean, efficient, well-tested solution on time, with strong focus on code quality and maintainability. My PR will be submitted in under 10 hours.

[DANeiraGarcia]

Hi team! I would like to claim this issue to implement the 'Why this API' rationale component. I can create the new clean component and integrate it into ApiCard following the accessibility guidelines. Please assign it to me!