feat(faq-inquiries): Add user association and delete functionality

[SamuelOshin]

Delete FAQ and Add User ID to FAQ

Description

This PR implements two changes:

1. Delete FAQ: Adds functionality to allow users to delete FAQ entries.
   DELETE /api/v1/faq-inquiries/{id}
2. Add User ID to FAQ: Modifies the FAQ model to include a user_id field, ensuring FAQs are associated with a specific user.

Related Issue (Link to issue ticket)

• [FEAT]: Endpoint to Delete FAQ Inquiry #1051 Implement FAQ Deletion
• FIX: Add user_id to FAQ Inquiries endpoints #1103 Add User ID to FAQ

Motivation and Context

• The Delete FAQ feature allows users to remove outdated or incorrect FAQ entries, improving data management.
• The Add User ID to FAQ ensures that FAQs are linked to the user who created them, enabling better access control and accountability.

How Has This Been Tested?

• Implemented unit tests for both features.
• Verified deletion functionality using Postman to ensure correct HTTP responses.
• Tested database migrations and API responses to confirm user_id is correctly stored and retrieved.
• Checked role-based access control for FAQ deletion to prevent unauthorized removals.

Screenshots (if appropriate - Postman, etc):

Types of changes

• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[joboy-dev]

Why do you think attaching user id to faq is a good idea??

[SamuelOshin]

can i modify the middleware in this format to allow public routes that doesn't need token ???

class UserMiddleware(BaseHTTPMiddleware):
    async def dispatch(self, request: Request, call_next):
        db = next(get_db())
        access_token = request.headers.get("Authorization")

        if access_token:  # Only check if a token is provided
            request.state.current_user = await user_service.get_current_user_or_none(access_token, db)
        else:
            request.state.current_user = None  # Allow anonymous users

        response = await call_next(request)
        return response

[joboy-dev]

There's no need for that Middleware in the first place
Thats why we use dependencies

[SamuelOshin]

There's no need for that Middleware in the first place
Thats why we use dependencies
Okay I'll make changes and use Depends()

[SamuelOshin]

Hi joedev i have made use of dependency and removed the middleware
thanks