Multiple improvements across multiple forks

[Hessesian]

I have tracked several improvements that went into multiple forks and added some of my own, including:

• added newline in the in memory buffer
• fixed migration issues across new versions of libraries
• added new sources of input to read from

I understand it's a lot of changes that are not fully coherent, and can't vouch for all of them, but I'm open to cherry picks or suggestions

[joepio]

@Hessesian since we both opened a PR in the last 24 hours with a lot of changes, and we're both keen on working on this project, maybe we should collaborate and try to merge our changes.

Stuff we both do:

• We both seem to have run rustfmt and clippy, so many changes will overlap
• Re-export lopdf
• Fix some of the panics

Stuff only your PR changes:

• switch to PHF (can be cherry-picked I think)
• Remove the Github Workflow
• Change pom to nom parser. Not sure if this is great if we need a github repo in the toml (makes the crate unpublishable).
• Add / export get_basefont.
• Switch to log. Is not very difficult to refactor I think. not sure what @jrmuizel thinks of course.
• Pass CID. Can be cherry picked
• Add newlines to plaintext. Not sure what this does, but can be cherry picked.

Stuff only my PR changes:

• Error handling (this is the biggest change by far). I have made many changes to lib.rs, including a lot of function signatures. That was a time-consuming task. As far as I can see, it looks like most changes from your PR to lib.rs are linting related. Is that right? If that's the case, I think it makes sense to take my lib.rs as a staring point.
• Tests
• Readme

[Hessesian]

Sure, seems to be wise to create separate pull request first for the formatting changes and common issues resolved, make sure it works and then we can do separate PR's for individual features that can be tweaked.

Can you maybe go ahead with your changes that don't clash ?

[joepio]

@Hessesian Is possible, but I'd prefer it if my PR was merged and we than cherry pick commits from yours. I'd gladly do that, but I want to know if the changes are OK to merge. @jrmuizel what is your opinion on this?

Might be useful to have a short video meet about all of this if you want. Reach me at joep@ontola.io