Split drasil printers

[JoeZZG]

#4831
drasil-printing is a new package, which contains the shared printing infrasturecture:
Printing.AST, Printing.LayoutObj, Printing.PrintingInformation, Printing.Import.* (all expression/document converters), Printing.Citation, Printing.Helpers, Plain.Print, Config

drasil-printers is now smaller and only contains format-specific printers (HTML, TeX, JSON, Markdown and Debug), and depends on drasil-printing

No other things changed

[balacij]

Restarted the CI because it was hanging on the system requirements.

[balacij]

Should drasil-printing be doing this much? I thought that these modules were meant to be kept in drasil-printers?

[JacquesCarette]

What I think this does, in part, is to separate the parts that are about specific output formats (kept in drasil-printers) from "the rest". So that drasil-printing becomes the 'awfully messy' package and drasil-printers may be regarded as fairly clear.

Of course, the new drasil-printing should not have so many exposed modules! It would be best to see how few of these modules need to be exposed.

[balacij]

Ah, ok. In that case, should LayoutObj, PrintingInformation, and Language.Drasil.Printing.AST stay in drasil-printers?

[JacquesCarette]

Once @JoeZZG trims down the exposed modules, we'll see. I guess one could see now, by staring at the dependency graph of the unsplit version.

[JacquesCarette]

What I think this does, in part, is to separate the parts that are about specific output formats (kept in drasil-printers) from "the rest". So that drasil-printing becomes the 'awfully messy' package and drasil-printers may be regarded as fairly clear.

Of course, the new drasil-printing should not have so many exposed modules! It would be best to see how few of these modules need to be exposed.

[JacquesCarette]

Better. But now we need to know why the others must be exposed.