Refactor: use value objects instead of primitive types

[mihailozarinschi]

Goals:

• Get rid of pkg/validate package
• Get rid of graphql/mutation.validator.go
• Have only valid objects everywhere in code
• Reduce possibility for passing parameters in functions in the wrong order
• Write code a bit faster because of better and faster suggestions from IDE with help of type matching

AC:

Common:

• ID
• Email refactor: use email value object instead of string primitive #95
• Slug
• URL

Login account:

• Password refactor: add password value object #97
• Session
• Token

User profile:

• Name
• ShortBio
• Vote (kudos)

Community:

• Name
• Tagline
• ExternalLinks
• CrosspostTelegramChannels
• WatchOption
• Vote (kudos)

Message:

• Title
• Body
• MentionedUsers
• Author
• PostedInCommunity
• RepliedToMessage
• WatchOption
• Vote

[zolotokrylin]

Should in Message also be Vote (kudos)? I mean theoretically pump=kudos, just different marketing.

[mihailozarinschi]

@zolotokrylin

The Message uses the full behavior of the Vote object, the User, and the Community use only the upvote (marketed as kudos).

I still don't know how it will be reused, maybe I'll add it in common.

[zolotokrylin]

@mihailozarinschi we actually were thinking to implement DUMP for the community, so others can express their opposite opinion. Reuse it, please. Let us have an option to downvote users and the community.
For example in Comunity, it is like rating + / - , with the user it is like "Freind / Report". We will be using these things later for sure. We just didn't get there.