Optionally make users created via the API set their password

What does this MR do?

This merge request makes it possible to specify that a user created via the API should receive an email asking them to set a password, rather than set a predefined password and not alert the user.

Are there points in the code the reviewer needs to double check?

Why was this MR needed?

In order to properly automate user creation, it is convenient not to have to communicate about passwords at all, but leave this up to the user.

Screenshots (if relevant)

Does this MR meet the acceptance criteria?

• Changelog entry added
• Documentation created/updated
• API support added
• Tests
  • Added for this feature/bug
  • All builds are passing
• Conform by the merge request performance guides
• Conform by the style guides
• Branch has no merge conflicts with master (if it does - rebase it please)
• Squashed related commits together

What are the relevant issue numbers?

Closes #1051 (closed) (Yes, that's an old one!)

mentioned in issue #1051 (closed)

added ~164274 ~13884 user management labels

added ~480950 label

@joostrijneveld Thanks, I had a few remarks.

assigned to @joostrijneveld

added 1 commit

• e58b0e83 - Optionally make users created via the API set their password

Compare with previous version

Thanks for looking into this! I've replied and amended the commit accordingly.

mentioned in issue #27878 (closed)

added 1 commit

• 6fab6d94 - Optionally make users created via the API set their password

Compare with previous version

changed milestone to %9.0

resolved all discussions

assigned to @rymai

Build failure is unrelated. @joostrijneveld Thanks!

mentioned in commit 6c62ec76

merged