Feat/us108 administration panel for jobs and employers

What does this MR do and why?

Merge Request related to the admin panel user stories 107-108.

baseUrl api/admin

[DELETE]

• deleteEmployer
• deleteJob

[GET]

• Un.ValidatedJobs
• Un.ValidatedEmployers

[POST]

• createJob
• createEmployer
• validateJob
• validateEmployer

[PUT]

• updateJob
• updateEmployer
• mergeJob
• mergeEmployer
• update user job or employer (setUserJob & setUserEmployer)

To do

• Unit tests

How to set up and validate locally (or on alpha)

Launch your backend services with docker-compose :

• docker-compose up -d database-ram
• docker-compose up -d mongo-express
• docker-compose up -d es01

Then run npm run start:dev

Use swagger if you need to test precisely some routes.

Use mongo express to edit quickly collections fields (switch a job from unvalidate to validate for instance).

• login password : ram,ram

MR acceptance checklist

To be completed by the chosen reviewer.

Quality

• Confirmed

1. For the code that this change impacts, I believe that the automated tests validate functionality that is highly important to users. If the existing automated tests do not cover this functionality, I have added the necessary additional tests or I have added an issue to describe the automation testing gap and linked it to this MR.
2. I have made sure that the sonar quality coverage is up to standards.
3. I have considered the impact of this change on the front-end, back-end, and database portions of the system where appropriate and applied.
4. I have tested this MR in all supported browsers or determined that this testing is not needed.
5. I have confirmed that this change is backwards compatible across updates (migrate up needs a migrate down), or I have decided that this does not apply.

Performance, reliability and availability

• Confirmed

1. I am confident that this MR does not harm performance, or I have asked a reviewer to help assess the performance impact.
2. I have considered the scalability risk based on future predicted growth.

Documentation

• Confirmed

1. I have prepared a squash commit to feed the changelog linked to the current milestone.
2. I have added/updated documentation (also updated if the changes feature a deprecation) or I have decided that documentation changes are not needed for this MR.

Security

• Confirmed

1. I have confirmed that if this MR does not contains any sensitive informations hidden in the changes.

Deployment

• Confirmed

1. When featured on a self-data project release, i have made sure my app version in the manifest and package.json is incremented and any relative changes to the permissions are clearly written and transmitted to Cozy.