server/schedule.c: Maintain separate variables for raw and resolved tracks.

GCC 9 correctly points out that, if `trackdb_resolve' fails, we try to
print a null pointer in the error message, rather than the offending
track name.

Fix this by not reusing the same variable for two different jobs with
overlapping lifetimes.