test(TopRivalriesTicker-timezone-boundaries): verify timezone normalization & calendar data boundary alignment

[tamilr0727-ux]

Description

Adds timezone normalization and calendar boundary test coverage for components/TopRivalriesTicker.tsx through the new test file components/TopRivalriesTicker.timezone-boundaries.test.tsx.

Changes

• Added tests simulating multiple timezone environments, including UTC, EST, IST, and JST.
• Verified activity and commit data are mapped to the correct calendar dates regardless of timezone offsets.
• Tested leap year handling to ensure continuous calendar rendering without missing or duplicated dates.
• Validated date formatting utilities across supported locale and timezone configurations.
• Added coverage for daylight saving time (DST) transition scenarios to ensure consistent date alignment.

Test Coverage

Implemented 5 test cases covering:

1. Correct date alignment across multiple timezone settings (UTC, EST, IST, and JST).
2. Accurate mapping of commits and activity records to their expected visual calendar dates.
3. Leap year boundary handling without gaps or incorrect date placement.
4. Consistent calendar date formatting across supported locales and timezone configurations.
5. Correct behavior around daylight saving time transition boundaries.

Validation

• All tests pass successfully with vitest run.
• Timezone environments are fully mocked for deterministic execution.
• No production code changes required.

Fixes #7030

Pillar

• 🎨 Pillar 1 — New Theme Design
• 📐 Pillar 2 — Geometric SVG Improvement
• 🕐 Pillar 3 — Timezone Logic Optimization
• 🛠️ Other (Bug fix, refactoring, docs)

Visual Preview

Cn Check in the Files Changed Section.

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.

[github-actions]

📦 Next.js Bundle Size Report (Gzipped Sizes)

✨ No significant bundle size changes detected.

📊 Summary of Totals

Category	PR Size	Base Size	Difference
Total JS	3883.44 KB	3883.44 KB	0 B
Total CSS	323.09 KB	323.09 KB	0 B

[Aamod007]

Hey! Thanks for adding timezone boundary tests to the TopRivalriesTicker. Validating locale offsets correctly guarantees our users in different regions don't see misaligned calendar dates.

I'm assigning level:intermediate, type:testing, and quality:clean.

Great catch, approving!

[github-actions]

🎉 Congratulations @tamilr0727-ux! Your PR has been successfully merged. 🚀

Thank you for contributing to CommitPulse. Your work helps us build a better tool for the community.

⚠️ Important for GSSoC Contributors:
You are strictly advised to join our Discord Server as it is mandatory for all GSSoC participants. All important announcements, point claims, and community discussions happen there.

Keep building! 💻✨