fix(FastAPI): Improve sqlite testing speed

This commit adds a new Arch dependency: `libeatmydata`, which
provides the `eatmydata` executable that stubs out fsync() operations.
We use `eatmydata` to run our sharness and pytests in Docker now.

With `autocommit=True`, required by SQLAlchemy to keep the
session up to date with external DB modifications, many fsync
calls are used in the SQLite backend; especially because we're wiping
and creating records in every DB-bound test.

**Before:**

- mysql: 1m42s (elapsed during pytest run)
- sqlite: 3m06s (elapsed during pytest run)

**After:**

- mysql: 1m40s (elapsed during pytest run)
- sqlite: 1m50s (elapsed during pytest run)

Shout out to @klausenbusk, who suggested this as a possible fix,
and it was. Thanks, Kristian!

Closes #120

Signed-off-by: Kevin Morris <kevr@0cost.org>

test/README.md

@@ -31,6 +31,10 @@ For all the test to run, the following Arch packages should be installed:
 - postfix
 - openssh
 
+Optional (faster testing)
+
+- libeatmydata
+
 Test Configuration
 ------------------
 
@@ -115,6 +119,12 @@ To run `pytest` Python test suites:
 
     $ make -C test pytest
 
+**Note:** For SQLite tests, users may want to use `eatmydata`
+to improve speed:
+
+    $ eatmydata -- make -C test sh
+    $ eatmydata -- make -C test pytest
+
 To produce coverage reports related to Python when running tests manually,
 use the following method: