Allow setting loglevel when creating a cron; include it in cron responses.

[drakkhen]

No description provided.

[invisig0th]

Seems like an opportunity to unify into something like reqValidLogLevel() somewhere central (maybe schemas.py?) to ensure consistency of the exception message/content 👍

[vEpiphyte]

Is setting the log level to INFO or DEBUG something that is supposed to have a change in behavior for how the cron job is actually executed?

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.72%. Comparing base (9b3b1da) to head (5eac1ea).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #4789   +/-   ##
=======================================
  Coverage   97.72%   97.72%           
=======================================
  Files         298      298           
  Lines       62504    62509    +5     
=======================================
+ Hits        61084    61089    +5     
  Misses       1420     1420           

Flag	Coverage Δ
linux	97.65% <100.00%> (-0.01%)	⬇️
linux_replay	93.41% <100.00%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[invisig0th]

Is setting the log level to INFO or DEBUG something that is supposed to have a change in behavior for how the cron job is actually executed?

Haha, good point! I think we plumbed the option but didn't implement the feature?

[vEpiphyte]

Per discussion, we're leaving the existing _runjob behavior as-is.