Adjust bounds for http-api-data and aeson

[ysangkok]

Fixes #1691. When all dependencies for all packages support aeson-2.2, we should adjust our code to be compatible.

[endgame]

I checked Hackage for releases with incorrect bounds, and they are 0.20, 0.19.1, and 0.19. All three of these packages import Data.Aeson.Parser in Servant.API.ContentTypes, and should have a metadata revision.

I am willing to do this in my capacity as Hackage Trustee. @phadej can you please ping me in the next couple of weeks if I should not do this?

[ysangkok]

Thank you @endgame , much appreciated

[endgame]

Is that a "yes, please go through and revise"?

[ysangkok]

@endgame Yes, I would appreciate if you applied the bounds from this PR to Hackage, also including older releases that import the Parser module. I don't have the Hackage permissions to do it.

[endgame]

By request, and as Hackage Trustee (jack), I have made the following revisions:

• servant-0.19: aeson >=1.4.1.0 && <3 to >=1.4.1.0 && <2.2
• servant-0.19.1: aeson >=1.4.1.0 && <3 to >=1.4.1.0 && <2.2
• servant-0.20: aeson >=1.4.1.0 && <3 to >=1.4.1.0 && <2.2

[ysangkok]

@endgame Would it be possible for you to also do the http-api-data bump that was included in this PR?

[endgame]

Which releases of servant and servant-server require revision?

[ysangkok]

@endgame: Which releases of servant and servant-server require revision?

Just servant-0.20 and servant-servant-0.20.

[endgame]

By request, and as Hackage Trustee (jack), I have made the following revisions:

• servant-0.20: http-api-data >=0.4.1 && <0.6 to >=0.4.1 && <0.7
• servant-server-0.20: http-api-data >=0.4.1 && <0.6 to >=0.4.1 && <0.7