An option to opt-out from using the default configuration file

Feature request

The default configuration file is great for tasks which are similar to the dataset and model used in it, but not really helpful for different use cases. My feeling is that I would benefit a lot if I can opt out from using it in favor of my own file. This would allow me to understand all the options and to validate that Hyrax indeed does what I ask it to do, or fails if an essential option is missed. It would also making testing of my code easier.

Before submitting
Please check the following:

• I have described the purpose of the suggested change, specifying what I need the enhancement to accomplish, i.e. what problem it solves.
• I have included any relevant links, screenshots, environment information, and data relevant to implementing the requested feature, as well as pseudocode for how I want to access the new functionality.
• If I have ideas for how the new feature could be implemented, I have provided explanations and/or pseudocode and/or task lists for the steps.

The issue names no files, tests, or entry points. Start by locating where Hyrax loads its default configuration and trace how user-supplied configuration is handled. Done means defining an explicit opt-out path, preserving custom configuration behavior, and adding tests for both opting out and missing essential options.