OAuth example should not infer org affiliation from the email field.

This example parses the user's email, returned from Google's authorization server, in order to determine if the user should have access:

https://github.com/AnswerDotAI/fasthtml-example/blob/6a985a7d00ff33a54a07aa9ff9a8dba77bbeb428/oauth_example/oa.py#L9

However, Google says not to do this, and to use the "hd claim" instead:


We should update the example to follow Google's advice.

An analogous change will also be needed in the fasthtml explainer notebook: https://github.com/AnswerDotAI/fasthtml/blob/main/nbs/explains/oauth.ipynb

It may appear elsewhere as well.

从 oauth_example/oa.py 中链接的行开始，然后检查 nbs/explains/oauth.ipynb，查找类似的基于电子邮件的隶属关系检查。在示例存储库和解释文档中搜索电子邮件字段在访问决策中的其他用法。完成的标准是两个示例都遵循 Google 关于 hd claim 的指导，并且不再存在基于电子邮件的组织推断。

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