Remove freckle-app module reexports

[chris-martin]

As we've broken stuff out of freckle-app we've given it module reexports to avoid affecting downstream, but these should get removed, because they prevent users from being aware that they're using freckle-app when they could be using a set of smaller packages instead.

[pbrisbin]

I think some work has happened here, but it's not totally done yet. Should we list things out so we can track progress? I'd be interested in pitching in and I wonder where we stand.

[chris-martin]

I think the only thing that has to be done here is remove

freckle-app/freckle-app/package.yaml

Lines 58 to 75 in d3288f1

	reexported-modules:
	- Freckle.App.Dotenv
	- Freckle.App.Env
	- Freckle.App.Http
	- Freckle.App.Http.Cache
	- Freckle.App.Http.Cache.Gzip
	- Freckle.App.Http.Cache.Memcached
	- Freckle.App.Http.Cache.State
	- Freckle.App.Http.Header
	- Freckle.App.Http.Paginate
	- Freckle.App.Http.Retry
	- Freckle.App.Prelude
	- Freckle.App.Exception
	- Freckle.App.Exception.MonadThrow
	- Freckle.App.Exception.MonadUnliftIO
	- Freckle.App.Exception.Types
	- Freckle.App.Test.Http
	- Freckle.App.Test.Http.MatchRequest

and add a changelog entry explaining which other packages users should now depend on.

[pbrisbin]

Oh nice, I didn't realize there was a reexported-modules feature we were using. I thought we had individual modules we had to move and remove. I can go ahead and do that.

[chris-martin]

In theory I had thought this would make an easier gradual transition for users, but in retrospect I don't see the point.