Add Add-SentryAttachment cmdlet with extension-based content-type defaults

[jamescrosswell]

Summary

Adds an Add-SentryAttachment cmdlet that wraps Scope.AddAttachment. When no -ContentType is supplied this is infered from the file extension so that the file preview in Sentry works for common 'text' files.

Mirrors sentry-python's pattern of delegating to a default mapping when the caller doesn't specify one — adds a small explicit table for some entries not in the OS MIME database (like the PowerShell extensions).

Usage

# Before — falls back to octet-stream, UI can't preview
Edit-SentryScope { $_.AddAttachment($PSCommandPath) }

# After — content type defaults to text/plain for .ps1
Add-SentryAttachment -Path $PSCommandPath

# Bytes with a filename hint
Add-SentryAttachment -Bytes $bytes -FileName 'data.json'

# Explicit override still wins
Add-SentryAttachment -Path $file -ContentType 'text/x-powershell'

The existing $_.AddAttachment(...) path is untouched — this is purely additive.

Example

This is what we see in Sentry after running the new sample:

Notes

• The broader fix (server-side extension fallback in the attachment viewer) should probably also happen in getsentry/sentry; this PR just covers the SDK-side.
• For unknown extensions we leave the content type unset, matching the previous behaviour.

Closes #32

[github-actions]

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against 2721fd1

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 9dba662. Configure here.}