Description

The Mastodon provider requests the `profile` scope during OAuth, but not all Mastodon instances support this scope. For example, noc.social rejects the OAuth request because it doesn't recognize `profile` as a valid scope.

The Mastodon OAuth spec uses `read:accounts` for profile data access, which is universally supported.

Steps to reproduce

1. Set up Postiz with Mastodon integration
2. Enter a Mastodon instance URL (e.g., noc.social)
3. OAuth flow fails due to unsupported `profile` scope

Expected behavior

OAuth should use `read:accounts` instead of `profile` for broader instance compatibility.

Environment

• Postiz: latest main branch
• Mastodon instance: noc.social (and likely others)