feat: moving user management service to django

Mostly refactor to match new values and structure from the backend. No functionality changes

assigned to @milho001

It seems this PR is mostly a style change, changing variable and key names; only few lines are actually required for the change to django (I think?).

As mentioned in the comments, im not too sure about changing to snake_case in a javascript codebase. Sticking with camelCase will keep the code base a bit more consistent and keep this PR smaller

added 10 commits

• f53e18ba...75c5be88 - 8 commits from branch main
• 73502457 - feat: moving user management service to django
• e60f2075 - chore: use camelcase

Compare with previous version

resolved all threads

waiting for postgres to be available in staging to be able to push

added 3 commits

• a46b3c24 - 1 commit from branch main
• 3959fb94 - feat: moving user management service to django
• 3f7c0d77 - chore: use camelcase

Compare with previous version

added 5 commits

• 3f7c0d77...e81a5689 - 3 commits from branch main
• 8785077e - feat: moving user management service to django
• dafb1c78 - chore: use camelcase

Compare with previous version

added 4 commits

• dafb1c78...dadc7940 - 2 commits from branch main
• 84888f82 - feat: moving user management service to django
• 5ccacc97 - chore: use camelcase

Compare with previous version

added 4 commits

• a12f813c - 1 commit from branch main
• d6929da1 - feat(qb): change qb context menu to right click
• d875f69c - feat: moving user management service to django
• 67e1ec99 - chore: use camelcase

Compare with previous version

added 4 commits

• 04f7df4f - 1 commit from branch main
• 237477ed - feat(qb): change qb context menu to right click
• 5dcade14 - feat: moving user management service to django
• d4436c3f - chore: use camelcase

Compare with previous version

enabled an automatic merge when all merge checks for d4436c3f pass

merged

This MR is included in version 1.106.0

The release is available on GitLab release.

Your semantic-release bot