Added pdf2image kwargs

[wolflu05]

While investigating some print quality issues, I noticed that there are some issues with the rendered png. So I first looked into to intermediately generated pdf, but everything looks fine there. So I suspect this has something todo with the png rendering. After a lot of playing with different options I found out that the pdf2image library has an optional setting (use_pdftocairo=True) to use pdftocairo instead of pdftoppm which is used by default.

pdftoppm (current)	pdftocairo
No sharp edges are rendered, which results in not always quadratical QR code pixels

So this PR adds an option to let the developer specify some custom options to pass over to pdf2image.convert_from_bytes(...). Not sure if we should use Cairo by default, as this may can break some printing plugins?

[netlify]

✅ Deploy Preview for inventree-web-pui-preview canceled.

Name	Link
🔨 Latest commit	f3aed6a
🔍 Latest deploy log	https://app.netlify.com/sites/inventree-web-pui-preview/deploys/65cdc78639b129000830e5ce

[SchrodingersGat]

I would suggest that we add a specific optional argument such as use_cairo=False rather than making the plugin developers discover and pass the use_pdftocairo argument themselves. I'd also be on board with making it default to True given the better fidelity in your results

[wolflu05]

I now added the direct use_cairo kwarg which is True by default now. But I still think it can have value to have all pdf2image arguments exposed to the developer, so I would keep that, what do you think?

[SchrodingersGat]

I now added the direct use_cairo kwarg which is True by default now. But I still think it can have value to have all pdf2image arguments exposed to the developer, so I would keep that, what do you think?

I agree, I am happy with the implementation as it stands