fix: enable-fts permanently save triggers

[chapmanjacobd]

I was wondering why my all my databases were giving wild search results. Turns out create_trigger was not sticking!

Running sqlite-utils triggers x.db shows [] after running enable-fts using the python api. Looking at the counts trigger it seems that is the right way to save triggers. triggers show up now

---

📚 Documentation preview 📚: https://sqlite-utils--498.org.readthedocs.build/en/498/

[codecov]

Codecov Report

Base: 96.37% // Head: 96.37% // Increases project coverage by +0.00% 🎉

Coverage data is based on head (75577e5) compared to base (d792dad).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #498   +/-   ##
=======================================
  Coverage   96.37%   96.37%           
=======================================
  Files           4        4           
  Lines        2401     2402    +1     
=======================================
+ Hits         2314     2315    +1     
  Misses         87       87           

Impacted Files	Coverage Δ
sqlite_utils/db.py	97.32% <100.00%> (+<0.01%)	⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[chapmanjacobd]

nevermind it was because I was running db[table].transform. The fts tables would still be there but the triggers would be dropped