[24.1] Log JobMappingExceptions at error level rather than debug

[natefoo]

This allows us to capture them in Sentry. Because TPV fail rules intentionally fail jobs with JobMappingException and we probably don't want those in Sentry, Marius suggested:

I would maybe add a log_level attribute to JobMappingException and have those fail rules be raised with raise JobMappingException("bla", log_level="info"). Or split the JobMappingException into JobMappingUnsatisfiable and JobMappingException or something like that?

Which would be good for dev (and TPV would need to change its raise).

How to test the changes?

(Select all options that apply)

• This is a refactoring of components with existing test coverage.

License

• I agree to license these and all my past contributions to the core galaxy codebase under the MIT license.

[jmchilton]

Rather than changing the client code - you could default to info and raise it as an error when it is called internally.

[mvdbeek]

That doesn't really help given TPV raises expected and unexpected exceptions of that type. I would start with changing TPV, don't see why we couldn't upgrade it.

[natefoo]

Just going to do this on the usegalaxy branch for now and a more robust solution will be implemented in dev.