Log INFO per task launch creates a large driver log

CoarseGrainedSchedulerBackend is logging an INFO every time a task is launched. Previously, only executor-related events were logged as INFO.

I propose dropping the task logging to a lower level, as task launches can happen orders of magnitude more than executor registration. (I've found the executor logs very useful, so I don't want to block out both via log4j configuration.)