Added users and companies with authentication

[nebyathhailu]

Description

This PR implements the RecruiterAuthentication model and all supporting logic for managing recruiter accounts and authentication in the Recos platform. It includes fields to store email, hashed password, profile data (first name, last name, and optional profile image), and timestamps for account creation and updates.
It handles workflows for signup, login, password reset (including forgot password processes), and securely manages password storage. The model also stores Odoo system access credentials—such as unique Odoo user ID, API key, email, and database name—linked to recruiters for secure verification and seamless integration with the Odoo HR system.
The main motivation is to enable secure authentication, recruiter profile management, and smooth synchronization with Odoo while maintaining system security and data integrity.

Fixes

Clickup

• Link
• Link
• Link

Figma

• Link

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Optimization
• Improvement
• Bug fix

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A - Manual testing was performed using Postman to validate the full authentication workflows, including recruiter signup, login, password reset, and forgot password endpoints. All requests returned expected responses with correct status codes and secure handling of credentials.
• Test B - Manual testing was conducted through the Django admin interface to verify recruiter account management, profile data updates, and timestamps for account creation and modification. This ensured that recruiter records and authentication details are correctly stored and manageable via the admin panel.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules