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.

Locate the final `me` resolver shown in the issue and inspect how the resolver context is populated from authorization headers. Verify whether it should return `context.user` rather than call `dataSources.userAPI.findOrCreateUser()`; done means the resolver reports the authenticated user consistently.

Written by the indexing model from the issue text.