[NEW] New API endpoints for Moderation feature

[Dnouv]

Proposed changes (including videos or screenshots)

A new API endpoint to fetch all of the reported messages within a certain timestamp.
A new API endpoint to hide the reported messages.
A new API endpoint to fetch the reported messages of a user
A new API endpoint to fetch reports by MessageId
Two new permission view-moderation-console and manage-moderation-actions

Issue(s)

Steps to test or reproduce

1. Please make sure there are reported messages on the server, and one should have the permission "View Moderation Console" ("Admin", "Owner", and "Moderator" will have this permission by-default) to successfully make the GET requests & the manage-moderation-actions to make the POST requests.

Test the API endpoint using the following:

curl --location --request GET 'http://localhost:3000/api/v1/moderation.getReports' \
--header 'X-Auth-Token: 7FNiLmgY7g77gxYOoa_IMkS6exghlv83YbM_Yt-w5__' \
--header 'X-User-Id: b4pSJS9BDK6xXgKea'

Or pass the latest and/or oldest parameters for filtered search:

curl --location --request GET 'https://localhost:3000/api/v1/moderation.getReports?latest=2023-09-30T13:42:25.304Z&oldest=2016-09-30T13:42:25.304Z' \
--header 'X-Auth-Token: ITIgsbLgjbIhIJTvC1XtgGnXiUD0kbN3wvj_Kg-_jfQ' \
--header 'X-User-Id: emfev66k8vpa8Qvxo'

To test the /moderation.markChecked endpoint (which hides the reported messages)

curl --location --request POST 'http://localhost:3000/api/v1/moderation.markChecked?userId/msgId=63d353bb8ead73b669b9480d' \
--header 'X-Auth-Token: flLCXwH2GL_NMxG8bwWtYc37g14uMScvGtsdtuesar1' \
--header 'X-User-Id: vYzJB8cvraoDg3Z5F'

To test the /moderation.reportsByMessage enpoint, we need a messageId; the message must have been reported:

curl --location --request GET 'http://localhost:3000/api/v1/moderation.reportsByMessage?msgId=73hkbsv90s9vs \
--header 'X-Auth-Token: 7FNiLmgY7g77gxYOoa_IMkS6exghlv83YbM_Yt-w5__' \
--header 'X-User-Id: b4pSJS9BDK6xXgKea'

GET: To test the moderation.user.getMessageHistory, we need the userId, the API returns all the messages that were reported for the userId provided

curl --location 'http://localhost:3000/api/v1/moderation.user.getMessageHistory?userId=nDaGJfjfbkFsuaECD' \
--header 'X-Auth-Token: ighlnlj-NpF7Ts' \
--header 'X-User-Id: nDaGJfjfbkFsuaECD'

POST: To test the moderation.user.deleteMessageHistory, we need the userId to delete any and all the messages that were reported for the provided userId

curl --location 'http://localhost:3000/api/v1/moderation.user.deleteMessageHistory' \
--header 'X-Auth-Token: gulgihkln-NpF7Ts' \
--header 'X-User-Id: nDaGJfjfbkFsuaECD' \
--header 'Content-Type: application/json' \
--data '{
    "userId": "7n56WrqYcNRutgYrx"
}'

Further comments

[debdutdeb]

please create raw models instead of meteor ones; take a look at apps/meteor/server/models/raw;

I think we're also reducing the use of underscore;

please also don't create meteor methods;

overall good job 👏🏼

[debdutdeb]

I'll review in a couple of hours.

[Dnouv]

Thank you! I just wanted to let you know that I have fixed it according to the comments.

[CLAassistant]

All committers have signed the CLA.