Add time_zone to /current/v2/me

[pastorhudson]

Related Product
API

Is your feature request related to a problem? Please describe.
The Current API (/current/v2/me) is scope-free but only exposes name/subdomain for Organization and email/first_name/last_name for Person. There's no way to read time_zone. To get it, an app has to call a product API like People, which forces it to request a broader OAuth scope just to render timestamps correctly.

Describe the solution you'd like
Expose time_zone from the Current API regardless of granted scope — add it to organization_renderable_attributes_enum (and ideally person_renderable_attributes_enum) and return it on /current/v2/me?include=organization, keeping it under the existing scope-free access model.

Describe alternatives you've considered
Calling the People API (/people/v2/me) works but requires the People scope solely to read a time zone. Inferring it client-side is unreliable and doesn't reflect the org's configured setting.

Additional context
Time zone is whoami-level context needed to render any timestamp correctly, independent of which products an app integrates.

I have..

• Reviewed the documentation found at https://developer.planning.center/docs
• Searched for previous issues asking for this feature request
• Removed all private information from this issue (credentials, tokens, emails, phone numbers, etc.)
• Reviewed my issue for completeness

[gkemmey]

@pastorhudson, thanks for the suggestion! time_zone has been added.