Implement self service user password change

[jordy2254]

Implements #263 base functionality to enable user to change their own password. This is a requirement for work intended to be done by me on #571 & #78.

[codecov]

Codecov Report

Attention: Patch coverage is 24.13793% with 22 lines in your changes are missing coverage. Please review.

Project coverage is 25.15%. Comparing base (8cdc4cd) to head (9abd61e).
Report is 2 commits behind head on master.

Files	Patch %	Lines
api/graphql/resolvers/user.go	0.00%	18 Missing ⚠️
api/graphql/models/user.go	63.63%	2 Missing and 2 partials ⚠️

Additional details and impacted files

@@             Coverage Diff             @@
##           master     #918       +/-   ##
===========================================
- Coverage   36.18%   25.15%   -11.03%     
===========================================
  Files          38       96       +58     
  Lines        1708     4428     +2720     
===========================================
+ Hits          618     1114      +496     
- Misses        934     3065     +2131     
- Partials      156      249       +93     

Flag	Coverage Δ
api	25.15% <24.13%> (-11.03%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[kkovaletp]

Merged to #910 after basic testing locally

[kkovaletp]

Hi @jordy2254, I've just got the feedback that not every user should have the possibility to change their own password: for instance, demo user shouldn't.

So, can you please do a small (I hope) update to this PR and implement a new switch per user on the Admin's settings page to allow or forbid self-change of the password?

This is now a crucial thing, which stops some users from using the latest build

[jordy2254]

Hey @kkovaletp
Yeah i can try to take a look at it tomorrow unfortunately I have a bit of a busy week ahead though. I guess for the meantime we can either;

• Give instructions to those on how to get back to the previous version
• revert the change on your branch entirely and merge back in again when it's ready (You've said in the past you're not a dev so happy to assist with this if needed.).

In the meantime I'll reach out on the discord channel and talk through the wider scope of the change and the changes I have planned and in the process of making to see if we want to wait it out.

[kkovaletp]

No need to revert the branch so far, also it is pretty clear how to revert to a previous commit locally and build from it for users, who reported this issue. So, we can wait for your update on the PR.

Sure, it is completely clear that you have your own plans, busy and free time. No need to rush and urgently develop an update! My request is just to update your list of prioritized tasks for our project, so that the next time, you'll work on it, you can start from this task and then continue your development of other features.