Stop using fork of amazonka (#976)

* snapshots: add sha256 and size to wireapp/amazonka

* pin amazonka to brendanhay/develop

The two issues mentioned in our previous snapshot are closed now:
    brendanhay/amazonka#466
    brendanhay/amazonka#490

snapshots/wire-2.0.yaml

@@ -45,6 +45,8 @@ packages:
 #
 # The archive corresponds to commit 52896fd46ef6812708e9e4d7456becc692698f6b.
 - archive: https://github.com/wireapp/amazonka/archive/wire-2019-01-25.tar.gz
+  sha256: b1cecd0e5e17cd41395ec56e4f6926e0c8bbeef493ff3a575bf7561b72db0525
+  size: 11128501
   subdirs:
   - amazonka
   - core

snapshots/wire-2.1.yaml

@@ -0,0 +1,24 @@
+# DO NOT MODIFY THIS FILE. See README.md to learn why.
+
+resolver: https://raw.githubusercontent.com/wireapp/wire-server/develop/snapshots/wire-2.0.yaml
+name: wire-2.1
+
+packages:
+# amazonka-1.6.1 is buggy: https://github.com/brendanhay/amazonka/issues/466
+# Therefore we pin an unreleased commit directly.
+#
+# More precisely, we pull just some libraries out of it,
+# the other packages weren't changed between 1.6.1 and this commit,
+# so we can use Stackage-supplied versions for them.
+# See https://github.com/brendanhay/amazonka/compare/1.6.1...9cf5b5777b69ac494d23d43a692294882927df34
+#
+# Once there has been made a new hackage release, we can use that instead.
+- archive: https://github.com/brendanhay/amazonka/archive/9cf5b5777b69ac494d23d43a692294882927df34.tar.gz
+  sha256: c3044f803a7652aee88fe600a97321175cdc1443d671246ba7ff78e14bf5b49f
+  size: 11137527
+  subdirs:
+  - amazonka
+  - amazonka-elb
+  - amazonka-redshift
+  - amazonka-route53
+  - core

stack.yaml

@@ -1,4 +1,4 @@
-resolver: snapshots/wire-2.0.yaml
+resolver: snapshots/wire-2.1.yaml
 
 packages:
 - libs/api-bot