feature: New rating framework

[TresorRw]

What does this PR do?

This PR includes the implementation of the new rating framework which gives the admin abilities to manage rating categories and their fields.
This new rating framework gives more detailed reviews across the team.
Short demo at loom

Description of Task to be completed?

Allow the admin to set rating categories and their fields which helps in making reviews for the team
This added new controllers, and services for each of the modules (Rating category, Rating Field) and refined the Overall Review to help in implementing this new rating framework.

Requirements

• Require dependencies installation
• Require .env update
• Require Database schema modification
• Documentation updated

How should this be manually tested?

To test this new you need to log in as admin if you want to manage category and their fields because he is the one to manage them.

To manage rating categories

POST /api/v1/ratingCategories send this request with a name in the request body (It is required, it will return an error if it's not provided)

GET /api/v1/ratingCategories returns all registered categories with their corresponding fields it exists

GET /api/v1/ratingCategories/<category_id> returns rating category if it exists otherwise its error

PATCH /api/v1/ratingCategories/<category_id> updates a rating category name

DELETE /api/v1/ratingCategories/<category_id> deletes a rating category

To manage rating fields

POST /api/v1/ratingFields send this request with a name and categoryId in the request body (It is required, it will return an error if it's not provided)

GET /api/v1/ratingFields returns all registered rating fields

GET /api/v1/ratingFields/<rating_id> returns rating fields if it exists otherwise its error

DELETE /api/v1/ratingFields/<rating_id> deletes a rating field

Creating A Review

This is where the change comes in, a user must provide this request body but with the correct data

{
    "comment": "This is so good",
    "revieweeId": "7f622ae6-af96-43a4-a3b1-cde78ecd5723",
    "reviewCycleId": "5b773104-9b85-4898-a169-d5b15b805bf5",
    "fieldReviews": [
        {
            "ratingFieldId": "6b4fc76e-8c02-4571-8358-042a311015f9",
            "ratings": 2
        },
        {
            "ratingFieldId": "13c58daa-4908-45e9-b334-6f6314ffcd81",
            "ratings": 1
        }
    ]
}

Note: fieldReviews key must be an array, if you provide wrong data you will get validation messages to tell you what is going on

Any background context you want to provide?

None

What are the relevant pivotal tracker stories?

Story ID: 187364953

Screenshots (if appropriate)

Questions:

• N/A

[leandreAlly]

@TresorRw it could be better if we have some validation middleware which accept the schema and return the result instead of importing this "valibot" in every files.

[TresorRw]

Thanks @leandreAlly, Let me look into that

[TresorRw]

Hello @leandreAlly, Kindly review again and let me know