Jobs vs Files#710

I’d like to propose introducing a job-based queue instead of a file-based queue.

In this model, a job represents a printable object, not a specific sliced file. Each job can have multiple pre-sliced variants assigned (e.g. for different printer types like P1S or A1).

The scheduler would then:

Assign the job to any compatible available printer
Automatically select the correct sliced file variant based on the assigned printer

This would allow a single job to be fulfilled flexibly across different printer types, instead of requiring separate queue entries per file/printer combination.

(Rewritten by ChatGPT for clearer intent)