Add OAuth token, introspect, and revoke endpoints

[Sumeet213]

#260

Summary

Add support for Notion's OAuth 2.0 endpoints to enable public integrations
and token management.

Changes

• Added OAuthEndpoint class with three methods:
  • token() - Exchange authorization codes or refresh tokens
  • introspect() - Validate OAuth tokens
  • revoke() - Revoke OAuth tokens
• Extended authentication to support Basic auth for OAuth client credentials
• Added VCR tests for introspect/revoke and mock tests for token exchange

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.53%. Comparing base (7762013) to head (7c4b89e).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #301      +/-   ##
==========================================
+ Coverage   99.51%   99.53%   +0.01%     
==========================================
  Files           7        7              
  Lines         411      426      +15     
==========================================
+ Hits          409      424      +15     
  Misses          2        2              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[tsinglinrain]

Hi, @Sumeet213 ! I noticed that in the OAuthEndpoint class of api_endpoints.py like this, the auth parameter is currently constructed as

auth = {"client_id": client_id, "client_secret": client_secret}

I was wondering if it might be more flexible to pass auth directly.

auth=kwargs.get("auth")

Letting users define the dictionary themselves — similar to how Client(auth=NOTION_TOKEN) works.

That said, I also noticed the official TypeScript SDK defines it this way, so it’s indeed a faithful translation.

Just sharing this thought, and please feel free to disregard.