feat: flattened context

[Natoandro]

Flatten profile fields in the context.

So instead of

{
    provider: 'github',
    accessToken: 'xxxxxxxxxxxxxxxxxxxxxxxxxx',
    refreshToken: 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx',
    refreshAt: 1704717676,
    profile: { id: '43663718' },
    exp: 1707280877,
    iat: 1704688876
}

we would have:

{
    provider: 'github',
    accessToken: 'xxxxxxxxxxxxxxxxxxxxxxxxxx',
    refreshToken: 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx',
    refreshAt: 1704717676,
    'profile.id': '43663718',
    exp: 1707280877,
    iat: 1704688876
 }

Motivation and context

It was impossible to get the nested id into a from_context injection.
Now we can inject .from_context("profile.id").

Migration notes

Checklist

• The change come with new or modified tests
• Hard-to-understand functions have explanatory comments
• End-user documentation is updated to reflect the change

[michael-0acf4]

How about enabling dot notation directly from context? I think it is best if we let the object as it is.
We split by the dots and walk the path iteratively, this should preserve compatibility with the current context implementation. wdyt?
Ref: https://github.com/metatypedev/metatype/blob/main/typegate/src/engine/planner/args.ts#L624

[zifeo]

@Natoandro adding to what @afmika is suggested, I believe this is on the app layer. I expect that the user of those auth methods write their own profiler function in deno (or else) that rewrite the context as they need and enrich it with the permissions they needed