fix: use finally block to always reset creating state in handleCreate

[akhilmodi29]

What does this PR fix?

Closes #1243

The "Add goal" submit button in the Goal Tracker widget gets permanently
stuck in a disabled "Creating..." state if the post-create sync or
reload throws an error.

Root Cause

setCreating(false) was only called at the end of the success path.
Any error after a successful POST meant it never ran.

Changes Made

• Moved form field resets inside the try block (only runs on success)
• Removed setCreating(false) from catch block
• Added finally { setCreating(false) } — button always re-enables

Files Changed

• src/components/GoalTracker.tsx

Testing Done

1. Open dashboard → Goal Tracker
2. Fill the goal form
3. Disconnect network → click "Add goal"
4. ✅ Button returns to enabled state after failure
5. Reconnect → try again → ✅ goal creates successfully

[vercel]

@akhilmodi29 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

[github-actions]

Thanks for your first PR on DevTrack! 🎉

A maintainer will review it within 48 hours. While you wait:

• Make sure CI is passing (type-check + lint)
• Double-check the PR description is filled out and the issue is linked
• Feel free to ask questions in Discussions if you need help

If you find DevTrack useful, a ⭐ star on the repo is always appreciated — it helps the project grow and attract more contributors!

[akhilmodi29]

@Priyanshu-byte-coder can you please review and apply the appropriate labels?

Suggested labels:

Difficulty:

• level:beginner — single file, ~10 line change, standard JS pattern

Quality:

• quality:clean — minimal fix, no side effects, clean diff

Type:

• type:bug — confirmed broken behaviour (button permanently disabled)
• type:fix — direct fix to broken state management
• type:ux — directly impacts user experience (stuck UI)

Validation:

• gssoc:approved — if the fix looks good to you