TeamRU function merge

[v0lv0]

TeamRU was designed to provide a way for participants to find team members and projects to work on during hackRU. It mainly stores data in a user object or a team object.

As the name implies team object stores information about the team, and the user object stores information about each member.
Each user object is created under each object by default, but it can be merged or separated by called some endpoints.

The user object is similar to the lcs objects, storing similar information, but it also contains information about the team or the path leading to the team object.

Proposals on how we can approach the issue:

1. adding a new type of object called team, adding a field under the user object that leads to the team, while the team object is a path leading back to the users.
2. adding many new fields under the user object that stores the team info in each user.
3. adding 2 fields in each lcs user object, "team_leader" and if "team_leader" is self. Then it can have a second field describing the team info.

However, for designs 2 and 3, major rewrites of the original teamRU are required since it was originally designed for work with objects on a team level. and for design 1, it might cause some conflicts with the current lcs code since it requires adding a new type of object.

TeamRU api: https://github.com/HackRU/teamRU/wiki/Using-TeamRU