fix : remove non-null assertion from pending array access

[tmdeveloper007]

Closes #502.

Summary of What Has Been Done:
Removed the non-null assertion (!) from pending array access after checking that pending is an array with length > 0. This was unnecessary and could mask potential type errors.

Changes Made:

• File: src/app/api/streak/freeze/route.ts
• Removed ! from pending![0] since we already check Array.isArray(pending) && pending.length > 0

Impact it Made:

• Cleaner code with no change in functionality
• Avoids potential runtime errors if the type assumptions are incorrect

[vercel]

@tmdeveloper007 is attempting to deploy a commit to the PRIYANSHU DOSHI's projects Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

GSSoC Label Checklist 🏷️

@Priyanshu-byte-coder — please apply the appropriate labels before merging:

Difficulty (pick one):

• level:beginner — 20 pts
• level:intermediate — 35 pts
• level:advanced — 55 pts
• level:critical — 80 pts

Quality (optional):

• quality:clean — ×1.2 multiplier
• quality:exceptional — ×1.5 multiplier

Validation (required to score):

• gssoc:approved — counts for points
• gssoc:invalid / gssoc:spam / gssoc:ai-slop — does not score

Type labels (type:*) are auto-detected from files and title. Review and adjust if needed.
Points formula: (difficulty × quality_multiplier) + type_bonus