Replace legacy identity and account dataset queries with Sprocket-native sources

[gankoji]

Summary

Move the public identity/account-oriented dataset queries off legacy mledb / mledb_bridge sources and onto Sprocket-native tables or views.

Why

Several public dataset queries still depend on legacy player/account bridges even though those concepts need to be retired after the main migration.

Candidate queries

• queries/public/players.sql
• queries/public/members.sql
• queries/public/trackers.sql
• queries/public/all_the_ids.sql

Scope

• Replace mledb_bridge.player_to_player joins with Sprocket-native identity/account sources.
• Remove reliance on legacy player/account fields where a Sprocket equivalent exists.
• Preserve downstream dataset shape where practical, or document intentional schema changes.

Acceptance criteria

• The identity/account dataset queries no longer require mledb or mledb_bridge.
• Any output schema changes are documented.
• CI/public dataset generation succeeds without those legacy joins.