This ticket is to track the work required to implement the spawn host setup script described below. Related tickets are tagged with the label DRI-spawn-host-script

The mongo repo has a spawn host setup script that will automatically extract tarballs and useful files into a ~/debug folder when a new spawn host is set up. We should look at doing the same for WiredTiger.

Using the mongo script as a reference our new script will need to:

• Check that we're running on a Linux host (Other platforms can be supported in subsequent tickets)
• Find the correct tarballs and filepaths in /data/mci/ to have the following:
  • The wiredtiger binaries
  • Core dumps
  • Shared library dependencies such as tcmalloc
  • Possibly the failing test and its logs, these will be already be inside the wiredtiger/cmake_build folder but we may want to move them to the top level ~/debug/ folder
• Move these files into the ~/debug folder in the correct locations
• Create a ~/.gdbinit file that configures the correct solib-search paths and source file paths
• Inform the user that the setup process has finished and they can now connect

Definition of Done
At the end of this ticket we should be able to ssh onto the new Linux spawn host, navigate to the ~/debug folder, and open coredumps from a failed test without needing to perform any of the manual steps we currently do such as extracting tarballs and setting solib-search-path. This process should work for all of our usual test suites (csuite, cppsuite, python tests, and test/format, etc) and for our wt util tool as well.