Operate hashed Member credentials (#165, #27)

[evdokimovs]

Part of #27
Fixes #165

Synopsis

We need to implement ability to check Member' s credentials by Argon2 hash provided by Control API.

Solution

Algorithm described in the #165.

Checklist

• Created PR:
  • In draft mode
  • Name contains Draft: prefix
  • Name contains issue reference
  • Has k:: labels applied
  • Has assignee
• Documentation is updated (if required)
• Tests are updated (if required)
• Changes conform code style
• CHANGELOG entry is added (if required)
• FCM (final commit message) is posted
  • and approved
• Review is completed and changes are approved
• Before merge:
  • Milestone is set
  • PR's name and description are correct and up-to-date
  • Draft: prefix is removed
  • All temporary labels are removed

[evdokimovs]

FCM

Operate hashed Member credentials (#168, #165, #27)

- add ability to specify credentials hash in Control API
- implement Web Client credentials verification via Argon2 hash received from Control API
- change Join URI format to: {{ Host }}/{{ Room ID }}/{{ Member ID }}?token={{ Token }}