Fix: When PDF/A rendering fails, add a consideration for the user to add args to override

[stumpylog]

Proposed change

Fixes #4067

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other (please explain):

Checklist:

• I have read & agree with the contributing guidelines.
• If applicable, I have included testing coverage for new code in this PR, for backend and / or front-end changes.
• If applicable, I have tested my code for new features & regressions on both mobile & desktop devices, using the latest version of major browsers.
• If applicable, I have checked that all tests pass, see documentation.
• I have run all pre-commit hooks, see documentation.
• I have made corresponding changes to the documentation as needed.
• I have checked my modifications for any breaking changes.

[shamoon]

Awesome, thanks!

[codecov]

Codecov Report

Merging #4083 (50dc9d3) into dev (d22a6fb) will decrease coverage by 0.03%.
The diff coverage is 40.00%.

@@            Coverage Diff             @@
##              dev    #4083      +/-   ##
==========================================
- Coverage   95.31%   95.29%   -0.03%     
==========================================
  Files         338      338              
  Lines       12779    12784       +5     
  Branches     1054     1054              
==========================================
+ Hits        12180    12182       +2     
- Misses        594      597       +3     
  Partials        5        5              

Flag	Coverage Δ
backend	94.05% <40.00%> (-0.04%)	⬇️
frontend	96.76% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed	Coverage Δ
src/paperless_tesseract/parsers.py	88.48% <40.00%> (-1.31%)	⬇️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns.