fix: eager load Position and TelegramUser to eliminate N+1 queries in…

[chuks68]

this pr closes #65 This PR resolves the N+1 query issue in UserDBConnector.get_users_for_notifications by eager loading the related Position and TelegramUser entities using SQLAlchemy's joinedload.
Configured positions and telegram_user relationships on the User model.
Updated the query in get_users_for_notifications to apply .options(joinedload(User.positions), joinedload(User.telegram_user)).
Re-mapped query outputs to return the expected (contract_address, telegram_id) tuple type to preserve the existing signature and behavior.

[YaronZaki]

Love the joinedload fix — clean way to kill the N+1. CI is failing on the test job though, so please address that and push a fix before we can land this.

[YaronZaki]

Hi @chuks68 — eager loading User.positions and User.telegram_user is the right call, and the explicit relationship definitions make this cleaner long-term. CI is currently failing on foreign-key constraint violations in the test suite:

insert or update on table "airdrop" violates foreign key constraint "airdrop_user_id_fkey"
insert or update on table "transaction" violates foreign key constraint "transaction_position_id_fkey"

This looks like a fixture-ordering issue (children being inserted before their parent user/position records), unrelated to the eager-loading change itself but exposed by it. Could you re-check the fixture setup in the affected tests so parents are seeded first? Once CI is green, easy merge. ✅