User management protocol

[lolski]

Release notes: usage and product changes

Declare user management messages and services, which lets the caller make user creation, update, deletion, and retrieval call through gRPC.

Implementation

Declare the associated gRPC services and Protobuf messages for user creation, update, deletion, and retrieval.

[typedb-bot]

PR Review Checklist

Do not edit the content of this comment. The PR reviewer should simply update this comment by ticking each review item below, as they get completed.

---

Trivial Change

• This change is trivial and does not require a code or architecture review.

Code

• Packages, classes, and methods have a single domain of responsibility.
• Packages, classes, and methods are grouped into cohesive and consistent domain model.
• The code is canonical and the minimum required to achieve the goal.
• Modules, libraries, and APIs are easy to use, robust (foolproof and not errorprone), and tested.
• Logic and naming has clear narrative that communicates the accurate intent and responsibility of each module (e.g. method, class, etc.).
• The code is algorithmically efficient and scalable for the whole application.

Architecture

• Any required refactoring is completed, and the architecture does not introduce technical debt incidentally.
• Any required build and release automations are updated and/or implemented.
• Any new components follows a consistent style with respect to the pre-existing codebase.
• The architecture intuitively reflects the application domain, and is easy to understand.
• The architecture has a well-defined hierarchy of encapsulated components.
• The architecture is extensible and scalable.

[farost]

Looking good, left some clarifications comments

[farost]

I like this, adds symmetry with databases.

[farost]

What do we use the User for in the request? Do we find the existing user by this message, and are name and password the updated fields then?