## Description Implement backend persistence for saved Pokémon teams using MariaDB and GraphQL, replacing the current `localStorage` implementation. Build on the existing frontend functionality and integrate with the existing Pokémon database. ### Acceptance criteria - Users can save multiple teams associated with their user ID. - Each team stores its name, format and Pokémon. - Pokémon order is preserved, with no duplicates within a team. - Users can retrieve, update and delete their saved teams. - Teams remain saved after closing and reopening the application. - Users can only access and modify their own teams. - Existing Pokémon data remains unaffected. - Backend functionality is covered by integration tests.