Feat: Fixed db migration issues from v3.2.0 to 3.3.0

[alithethird]

When migrating from v3.2.0 to v3.3.0 we had to drop some triggers by hand. This PR makes it so that the triggers are dropped automagically.

DROP TRIGGER IF EXISTS invites_user_id_readonly ON invites;

DROP TRIGGER IF EXISTS invites_redeemed_at_readonly ON invites;

DROP TRIGGER IF EXISTS user_api_keys_scopes_readonly ON user_api_keys;

Overview

Rationale

Juju Events Changes

Module Changes

Library Changes

Checklist

• The charm style guide was applied
• The contributing guide was applied
• The changes are compliant with ISD054 - Manging Charm Complexity
• The documentation is generated using src-docs
• The documentation for charmhub is updated.
• The PR is tagged with appropriate label (urgent, trivial, complex)

[mthaddon]

LGTM, thx!

[github-actions]

Test coverage for f26f811

Name              Stmts   Miss Branch BrPart  Cover   Missing
-------------------------------------------------------------
src/charm.py        373     41     94     15    88%   184, 192-193, 205, 337->345, 378->383, 395, 583-585, 590-591, 603-605, 610-611, 623-625, 648-650, 692->exit, 702->exit, 751-754, 764-765, 789-790, 802-803, 830-832, 834->839, 836-837, 879-880, 896-897, 907->exit, 921
src/database.py      29      1      8      1    95%   56
-------------------------------------------------------------
TOTAL               402     42    102     16    88%

Static code analysis report

Run started:2024-09-24 13:37:14.111560

Test results:
  No issues identified.

Code scanned:
  Total lines of code: 2458
  Total lines skipped (#nosec): 2
  Total potential issues skipped due to specifically being disabled (e.g., #nosec BXXX): 0

Run metrics:
  Total issues (by severity):
  	Undefined: 0
  	Low: 0
  	Medium: 0
  	High: 0
  Total issues (by confidence):
  	Undefined: 0
  	Low: 0
  	Medium: 0
  	High: 0
Files skipped (0):

[merkata]

to the moon 🚀