Improve the Member API entity to take actual Member objects instead of User

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

As noted in several comments:

This is weird that the Member API entity takes a User object rather than a Member object. That being said, from a pragmatic point of view, we're actually exposing more user attributes than member attributes in this entity so that's probably why the current implementation is like it is. :)

Edited by 🤖 GitLab Bot 🤖