Handle "expected" cron errors

Errors like `Error: No resources available to run the job with action...` will occur when a job is attempted to be run but application-level currency locks stopped it and returned early.

This is not a true error, as it's expected to some degree. So we should better handle these, and perhaps provide a more customized metric for keeping an eye on them.

Start by locating the code that emits `No resources available to run the job with action...` and tracing how application-level currency locks return early during a job attempt. Determine how expected cases are currently reported and what metric behavior is required; the work is done when these cases are handled distinctly without being treated as true errors.

Written by the indexing model from the issue text.