fix: change SENTRY_TOKEN to SENTRY_DSN

[mifuyutsuki]

Pull Request Type

• Feature addition
• Bugfix
• Documentation update
• Code refactor
• Tests improvement
• CI/CD pipeline enhancement
• Other: [Replace with a description]

Description

Change references to SENTRY_TOKEN with SENTRY_DSN in docs (Error Tracking guide) and messages (interactions.ext.sentry:setup on error), in accordance with Sentry.io docs. This should avoid confusion by users possibly adding a Sentry.io auth token on setup.

Added as fix as this PR also includes a fix on an error when specifying dsn="dsn" but not token="dsn" on extension setup.

Changes

• interactions.ext.sentry:setup: Add argument dsn in place of token
  • token is moved back and is accessible as a kwarg, avoiding breaking changes. However, dsn will take precedence when available.
  • This avoids an error when using dsn="dsn" without specifying token="dsn".
• Replace references to token=SENTRY_TOKEN with dsn=SENTRY_DSN. Instead, an error would be emitted if both are unspecified or None.
• Edited the Error Tracking guide accordingly
  • Added small information on what DSN looks like (a url).

Related Issues

Test Scenarios

A ZeroDivisionError event should appear on the Sentry.io project corresponding to the DSN. The DSN below is an example.

from interactions import Client, slash_command, SlashContext

@slash_command(name="test", description="Test command")
async def test_cmd(ctx: SlashContext):
  plant = 1 / 0
  await ctx.send("This message is never reached")

bot = Client()
bot.load_extension("interactions.ext.sentry", dsn="https://...@o1.ingest.sentry.io/1048576")
bot.start("token")

The load_extension should still work with token kwarg:

bot.load_extension("interactions.ext.sentry", token="https://...@o1.ingest.us.sentry.io/1048576")

Keyword dsn overrides token when available:

bot.load_extension("interactions.ext.sentry", token="bad link", dsn="https://...@o1.ingest.us.sentry.io/1048576")

The error message should show, this time for "no Sentry DSN".

bot.load_extension("interactions.ext.sentry")

Python Compatibility

• I've ensured my code works on Python 3.10.x
• I've ensured my code works on Python 3.11.x

Checklist

• I've run the pre-commit code linter over all edited files
• I've tested my changes on supported Python versions
• I've added tests for my code, if applicable
• I've updated / added documentation, where applicable

[AstreaTSS]

Not sure if this should be classified as a feat or a fix (I'm leaning towards feat/fix), but either way, looks solid.

[silasary]

Thanks