fix: Lazy initialize Firebase only when needed

[Likheet]

• Added lazy initialization for Firebase services
• Created getter functions to ensure Firebase is initialized only when accessed
• Improved error handling and development experience
• Added proper mock implementations for development mode
• Updated auth.ts to use new getter functions

Fixes #7

[Copilot]

Pull Request Overview

This PR implements lazy initialization for Firebase services to ensure they are configured only when needed, while also introducing mock implementations and improved error handling in development mode.

• Introduces lazy initialization and getter functions for Firebase services.
• Improves error handling by conditionally using mocks in development mode.
• Updates Firebase authentication methods to utilize the lazy initialization.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
lib/firebase/config.ts	Refactors Firebase initialization with lazy-loading; adds mocks and improved error logs.
lib/firebase/auth.ts	Modifies auth functions to use the new getter functions and initialization checks.

[Copilot]

The 'else if' block after the try-catch appears to be unreachable or misplaced, which may result in inconsistent behavior in development mode. Consider revising the control flow to ensure that mocks and warnings are applied appropriately when configuration is incomplete.

Suggested change

	} else if (process.env.NODE_ENV === 'development') {
	console.warn(
	'Firebase configuration is incomplete. Running in development mode with mock services.\n' +
	'To use real Firebase services, ensure all required environment variables are set in your .env.local file.'
	);
	}
	// Removed unreachable else if block.