Check configuration consistency between runs and existing auxiliary files

Hermes does not currently verify whether existing auxiliary files were generated using a configuration compatible with the current run. This can lead to situations where outdated auxiliary files are reused even though the configuration has changed, causing the new settings to be ignored.

@ctena I propose adding metadata to the auxiliary files containing the configuration used to generate them. Hermes should then check, at runtime, whether the metadata configuration matches or is compatible with the current configuration. If they are not compatible, Hermes should raise a warning or an error, I'm not sure what the best option would be.