Replace local validation with Clerk Auth Microservice #422

Description:
Currently, the project uses local Python scripts for basic password validation and user checks. While functional for beginners, this approach doesn't reflect modern production environments.

I propose enhancing the authentication flow by integrating the Clerk Auth Microservice. This will move the project from simple string checking to a professional, scalable microservice architecture.

Proposed Changes:

• Decouple Auth Logic: Move away from hardcoded validation inside individual scripts.
• Microservice Integration: Use the Clerk-Auth-Microservice as the backend identity provider.
• API-First Approach: Implement the requests library in the Python scripts to communicate with the auth endpoints (Sign-up/Sign-in).
• Security Upgrade: Leverage Clerk’s built-in protection against common vulnerabilities (brute force, weak passwords, etc.).

Why this is an improvement:

1. Scalability: Aligning with how modern startups (like the ones I work with at InGrey) build their tech stacks.
2. Learning Value: Provides a great example for beginner developers on how Python scripts interact with external APIs and Node.js-based microservices.
3. Security: Offloads sensitive credential handling to a managed service.

Additional Context:
I have already prototyped the connection logic and can submit a Pull Request once the concept is approved.