feat: fix auth context, profile pic storage

[AnkushSarkar10]

• fixed all instances of using id = '1'
• user profile pic in firebase storage
• fixed bug with view habit page not opening for new habits
• editprofile will open with users current data filled in in the input

[AnkushSarkar10]

• feat: fix auth context, profile pic storage #162 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[Copilot]

Pull Request Overview

This pull request replaces hardcoded user IDs with a dynamic retrieval of the current user's ID and improves profile picture handling from Firebase storage. Key changes include:

• Replacing all instances of the hardcoded user ID '1' with the getCurrentUserId() helper.
• Adding getCurrentUser and getCurrentUserId functions in the auth module.
• Updating profile picture fetching and habit view logic to better reflect the authenticated user.

Reviewed Changes

Copilot reviewed 15 out of 15 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
src/core/auth/index.tsx	Added new helper functions to retrieve current user data and ID.
src/components/modify-habit-entry/modify-entry-modal.tsx	Replaced hardcoded user ID with dynamic current user ID.
src/components/habit-card.tsx	Replaced hardcoded user ID with getCurrentUserId() for habit card display.
src/app/habits/view-habit.tsx	Updated filtering and UI logic to use the dynamic user ID.
src/app/auth/create-edit-profile.tsx	Modified profile creation/edit logic to rely on getCurrentUserId() and improved default image usage.
src/api/users/*	Replaced usage of getUserById with getUserWithRelationshipById where applicable and updated user ID acquisition.
src/api/notifications/*	Replaced hardcoded user ID with getCurrentUserId() for notifications logic.
src/api/habits/*	Updated habit mutations to use the current user's data and getCurrentUserId() instead of a hardcoded ID.

Comments suppressed due to low confidence (2)

src/api/habits/firebase-mutations.ts:49

• Both displayName and username are set to currentUserData.username; consider using a separate field (e.g., currentUserData.displayName) for displayName to accurately represent user data.

displayName: currentUserData.username,

src/api/habits/firebase-mutations.ts:13

• [nitpick] The import path for getCurrentUserId is inconsistent with other files (which import from '@/core'). Consider using a consistent import path to avoid potential confusion.

import { getCurrentUserId } from '@/core/auth';