Separate draw logic from list of operation logic

[rsaxvc]

Currently, libcutter operates on a single operation/command at a time.

We should transition to a more flexible list-of-operations approach. Ex:

• SVG parsing becomes a file -> list-of-operations
• Rescale becomes (list-of-operations, scale) -> list-of-operations
• Cutting becomes list-of-operations -> device
• Bounds check becomes (list-of-operations, device, deviceConfig) -> boolean
• operation order optimization(path/cut order optimization #38 ) becomes list-of-operations -> list-of-operations

[citelao]

This could also be used to unify the GCode and SVG parsers. All parsing => operations => optimization & output.

[rsaxvc]

That's what I'm thinking. Also things like scale-to-fit and bounds check pre enforcement before potentially ruining a big sheet of expensivium.