Add Spanish and Tamil Translation Tests for Enhanced Coverage

[codecrafted1]

Description
Adds missing language test coverage for Spanish (es) and Tamil (ta).

Changes made
Added lib/i18n/languages/es.test.ts
Added lib/i18n/languages/ta.test.ts
Verified language key existence
Verified getLabels(lang) returns the correct translation object
Verified all required BadgeLabels properties are present
Verified expected translation strings match exactly

Fixes #8190

Pillar
🎨 Pillar 1 — New Theme Design
📐 Pillar 2 — Geometric SVG Improvement
🕐 Pillar 3 — Timezone Logic Optimization
🛠️ Other (Bug fix, refactoring, docs)
Visual Preview
N/A (test-only change)

Checklist before requesting a review:
I have read the CONTRIBUTING.md file.
I have tested these changes locally (localhost:3000/api/streak?user=YOUR_USERNAME).
I have run npm run format and npm run lint locally and resolved all errors (CI will fail otherwise).
My commits follow the Conventional Commits format (e.g., feat(themes): ..., fix(calculate): ...).
I have updated README.md if I added a new theme or URL parameter.
I have started the repo.
I have made sure that i have only one commit to merge in this PR.
The SVG output matches the CommitPulse "premium quality" aesthetic standard (no raw elements, smooth animations, correct fonts).
(Recommended) I joined the CommitPulse Discord community for contributor discussions, mentorship, and faster PR support.
Labels
testing
good first issue
gssoc26

[vercel]

Someone is attempting to deploy a commit to the jhasourav07's projects Team on Vercel.

A member of the Team first needs to authorize it.

[retenta-bot]

This PR enhances our translation coverage by adding tests for Spanish and Tamil, ensuring that our application supports these languages effectively. This aligns with our previous decision to improve internationalization and testing practices. Thank you for your contribution, and I look forward to your updates!

[github-actions]

👋 Hey @codecrafted1! Thanks for your contribution! 🎉

Unfortunately, this PR has been automatically closed because it is not linked to any open issue.

To resolve this, please do the following:

1. Link a valid open issue by editing your PR description to include a closing keyword (e.g., Fixes #<issue-number>).
2. Reopen this PR once the link is added.

💡 You can link multiple issues if needed (e.g. Fixes #12, Closes #34).
If you're working on something that doesn't have an issue yet, please open one first and then link it here.

We look forward to reviewing your PR once an issue is linked! 🚀