Don't read .psqlrc for automated DB export

[domodwyer]

The dump_db_and_reimport_dump test fails on my machine because my .psqlrc sets the session into "read-only" mode by default, causing the import step to fail.

Looking at how this is used, I don't think sourcing the .psqlrc file is intended - a user might have it do anything! It's not uncommon to SET various options on the connection, some of which might cause problems (timeouts, search paths, etc).

---

• fix: don't read .psqlrc for automated DB export (0c492d2)

  The dump_db::run_psql() function spawns a psql child process to run a an
  export script, but psql will automatically load and execute the content
  of the user's ~/.psqlrc file if it exists and execute it before the
  export script.
  
  The statements executed from the psqlrc file might change connection
  parameters (for example, the search path) in a way that causes the
  script to fail.
  
  This commit stops psql sourcing the psqlrc file at startup, meaning the
  connection should always be in a fresh / clean state.
  

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.28%. Comparing base (e80b035) to head (0c492d2).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #9246   +/-   ##
=======================================
  Coverage   89.27%   89.28%           
=======================================
  Files         282      282           
  Lines       28589    28590    +1     
=======================================
+ Hits        25524    25526    +2     
+ Misses       3065     3064    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Turbo87]

I wasn't even aware such a file is supported... 😅

While I don't yet see the reasons for setting such things globally, ignoring the file for this call doesn't hurt either, so thanks for the PR :)