fix: Support SQLite in migration 0079_apitoken_data

[Om-A-osc]

Issues

• Closes: N/A

Changes

• Fixed a migration failure when using SQLite caused by a PostgreSQL-specific query.
• Added a conditional check for the database backend and used the appropriate query for each.
• Ensured that migrations run correctly for both PostgreSQL and SQLite setups.

The migration file scanpipe/migrations/0079_apitoken_data.py was checking if a table existed using PostgreSQL-specific syntax:

cursor.execute(
    "SELECT EXISTS (SELECT 1 FROM information_schema.tables "
    "WHERE table_name = 'authtoken_token')"
)

This syntax works for PostgreSQL but not for SQLite. SQLite uses a completely different system table called sqlite_master.

I updated the migration to detect which database is being used and use the correct SQL syntax for each:

Checklist

• I have read the contributing guidelines
• I have linked an existing issue above
• I have added unit tests covering the new code
• I have reviewed and understood every line of this PR