fix: pass auth_instance to sentry middleware

[suvanbanerjee]

Pull Request

Description

Sentry was only showing client IP addresses and was not logging user email information because the auth instance was not being passed through.

Fixes #329

Checklist:

• My code follows OCF's coding style guidelines
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• I have checked my code and corrected any misspellings

[suvanbanerjee]

@braddf I decoded the current JWT and these are the fields present:

{
  "trial_ends_at": "...",
  "https://openclimatefix.org/email": "...",
  "iss": "https://nowcasting-pro.eu.auth0.com/",
  "sub": "google-oauth2|10...34",
  "aud": [
    "https://api.nowcasting.io/",
    "https://nowcasting-pro.eu.auth0.com/userinfo"
  ],
  "iat": 1781842439,
  "exp": 1782706439,
  "scope": "openid profile email offline_access",
  "azp": "...",
  "permissions": [
    "read:trial"
  ]
}

When we add the organization_id, what key should we use to store it in the JWT?

I can also add it to the Sentry middleware so it gets attached to Sentry events.

[braddf]

@suvanbanerjee the org id should be stored/fetched already here:

https://github.com/openclimatefix/quartz-api/blob/main/src/quartz_api/internal/middleware/auth.py#L120

So you can use that key too

[peterdudfield]

Don't worry about organization I'd, just ignore that

[peterdudfield]

if the email is there, thats fine

[suvanbanerjee]

@suvanbanerjee the org id should be stored/fetched already here:

https://github.com/openclimatefix/quartz-api/blob/main/src/quartz_api/internal/middleware/auth.py#L120

So you can use that key too

I used the get_org_id_from_authdata function rather than accessing app_metadata["hubspot_id"] directly. That way, if the underlying key ever changes in the future, we only need to update it in one place instead of everywhere it's used.