🐛 Only initialize WAL once

[aaronleopold]

• I added a new field to the server_config called initial_wal_setup_complete. As the name suggests, it will be updated to true once Stump sets the journal_mode to WAL. It is important to NEVER update this flag manually.

  • The boot flow is now as follows: 1. run migrations 2. check for/create server_config 3. check for wal flag and initialize it if needed

• I added a new sub-command system to the CLI, however you shouldn't need to use it:

   ❯ ./stump_server system --help
   Subcommands for interacting with the system commands
  
   Usage: stump_server system <COMMAND>
   
   Commands:
     set-journal-mode  Set the journal mode for the database. Please use this command with caution!
     help              Print this message or the help of the given subcommand(s)
    
   Options:
     -h, --help  Print help
  
   ❯ ./stump_server system set-journal-mode --help
   Set the journal mode for the database. Please use this command with caution!
  
   Usage: stump_server system set-journal-mode --mode <MODE>
  
   Options:
       --mode <MODE>  The journal mode to set
   -h, --help         Print help

• I also added the mocking feature to Prisma to enable better testing down the road