fix(admin): restore current password input on profile page

[remidej]

What does it do?

Changes on the profile page:

• restores the current password input, as it it needed by the backend to change password
• avoids passing an empty password string if the user didn't touch the password input. This is what prevented users from saving

Why is it needed?

To allow users to save their changes on the profile page.

How to test it?

Go to the profile page, make changes (both with and without password changes), then try to save.

Related issue(s)/PR(s)

fixes #18678

[joshuaellis]

So a user needs to pass their current password to change their password?

IMO we should add a unit test for this, because it was very unclear why we had the "current password" field 🙂

[remidej]

So a user needs to pass their current password to change their password?

@joshuaellis yes it is, because it's different from the password recovery feature which works via an email

[joshuaellis]

Do you think we could get the types to represent this? i.e if password is present in the object then current password is not optional... just wondering more solutions to tighten this up for the future.