This is necessary because the extensive changes in `epdfinfo` do not
get picked up by third party package management systems unless they
enter Melpa Stable.

This mismatch caused a number of issues, which I expect this bump will
now fix. Thanks to @cyrilarnould and @barslmn for pointing this out.

I am also using this bump to close long-open install issues. The idea
here is that these issues are being lost. I would rather everyone
upgrade to the latest versions of `pdf-tools` and `epdfinfo` and then
re-report the issues if they still exist.

Please note: as of this release, users are not expected to manually
set anything on their machines during installation. (for example:
`$PKG_CONFIG_PATH`). The installation should *just work*. If it does
not, please open a ticket so that we can track it.

Fixes: #213
Closes: #177
Closes: #216

The current href style was not working on Github, which is really
irritating. This commit fixes the issue.

Closes: #198

From the comments in the PR, @smithzvk explains the changes:

 > I was bugged that it didn't pick up the hue from the background,
 > however, so I made the all color a/b parameters start from the a/b
 > parameters of the BG color. This makes the PDF background (white)
 > map to your BG color and PDF foreground (black) map to your FG
 > color, which can be set to your theme background making it seem
 > pretty seamless. Note that if you set your BG and FG to a color
 > theme without zero saturation (a gray tone of some sort), then you
 > recover the original behavior.
 >
 > I also reinstated the cached transforms for background and the last
 > color computed.
 >
 > I also refactored the loop to move the switch statement outside of
 > the loop. It is more repetitive, but it was needed to get rid of
 > some warnings about potentially uninitialized variables. It should
 > also be faster as the branch was removed from the loop.
 >
 > I also ditched the gamma correction as it seemed to be doing the
 > wrong thing and I never had a theoretical reasoning for it. I can
 > get similar results if I just set my BG color to something like
 > gray5 instead of black. Barely a difference in background but the
 > hinting on the fonts is showing again. The root of my issue may
 > have always been some kind of display calibration issue.

Closes: #197

Uses the Lightness values from the `pdf-view-midnight-colors` `fg` and
`bg` to scale the inverted color's lightness. Band-aid till better
method is found.

Relates to: #69

The currently used "medium" one has been deprecated, as mentioned
here:
https://discuss.circleci.com/t/macos-resource-deprecation-update/46891

Setting `pixel-scroll-precision-mode` to nil is not sufficient to disable
the mode locally.

Updates: #124

In Void Linux most heading/development files are separated from the "main" packages and are stored on `${package-name}-devel`. The autobuild for Void fails because it tries to find `cairo-devel`, which contains `cairo`, respectives headers and other dependencies.

This Pull Request adds `cairo-devel` to the `PACKAGES` variable

This commit enables @smithzvk's work in #69 as the default in
`pdf-tools`. It works well for all the PDFs I have tested with.

The previous behaviour can be enabled by setting
`pdf-view-midnight-invert` to `nil`, if required.

This inversion method attempts to maintain the color hue and saturation but
inverts the lightness using the OKLab color space[^1].

[^1]: https://bottosson.github.io/posts/oklab/

* server/epdfinfo.c (image-recolor): Add feature to support the OKLab
inversion method functionality

* lisp/pdf-view.el (pdf-view-midnight-invert): Add new variable to
invert the image color lightness while maintaining hue.

(pdf-view-midnight-minor-mode): Account for above.

* lisp/pdf-info.el (pdf-info-query--parse-response): Handle changes to
:render/usecolors command

Closes: #69
Closes: #169
Closes: politza/pdf-tools#698
Closes: politza/pdf-tools#608

We need a dedicated command for rotation since when `pdf-tools`
redisplays the image, the `:rotation` image-property is lost.
Pdf-tools redisplays the images when changing pages, zooming in/out,
setting the slice, etc. so this is essential to have.

A variable is used simply because `pdf-tools` already uses a variable to
keep track of the current scaling.

* lisp/pdf-view.el (pdf-view--current-rotation): Add new variable to
keep track of angle.
(pdf-view-create-page): Account for above.
(pdf-view-mode-map): Add the new command under "R".
(pdf-view-rotate): Add new command.

Fixes: #152
Closes: #165