Deal with batchless process data from "slurm" node that happens to be interactive

[lars-t-hansen]

(This is a backend problem not a dashboard issue.)

The 183K cores here makes everything be wrong. Not sure what job=0 is about either.

[lars-t-hansen]

"Job 0" is an interactive job. gpu-3 does not actually run Slurm.

This explains the weird peak - this is bug #77 again, once again on a batchless system.

[lars-t-hansen]

Probably the reality is going to be that the admins will make nodes interactive or not without thinking about sonar. So we probably need to add functionality to Jobanalyzer or Sonar to recover. It is definitely possible to do it in Sonar - as there will not be a slurm job ID, we can assume that the job is interactive and we should use the other algorithm instead.