Me Resolver on final is misleading

This is the resolver for me on final

```
me: async (_, __, { dataSources }) =>
dataSources.userAPI.findOrCreateUser(),
```

However it could (and probably should) be

```
me: async (_, __, context) => context.user
```

which is the logged in user authenticated by the authorization headers.

找到 issue 中显示的最终 `me` resolver，并检查 resolver context 如何从授权 headers 中填充。验证它是否应该返回 `context.user`，而不是调用 `dataSources.userAPI.findOrCreateUser()`；完成标准是 resolver 始终一致地返回经过身份验证的用户。

由索引模型根据 Issue 内容生成。