Fix the SQLite write transaction test
The SQLite database test for
WriteTransaction sometimes fails with "database table is locked". This is most likely due to the fact that we don't properly set a value for the
sqlite3_busy_timeout. This results in SQLite immediately throwing an error when a write/immediate transaction is initiated while another one is already active, instead of waiting for the first one to end.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information