fix(redstone): Re-deploy SpokePool (#578)

The initial Redstone deployment only deployed an implementation
contract, not a proxy. This should have been recognised and corrected
during deployment, but was overlooked and not discovered until testing. 
The deployment scripts have been updated to make it more difficult to 
do this accidentally in the future.

Author: pxrl

deployments/deployments.json

@@ -98,7 +98,7 @@
   },
   "420": { "SpokePool": { "address": "0xeF684C38F94F48775959ECf2012D7E864ffb9dd4", "blockNumber": 17025501 } },
   "690": {
-    "SpokePool": { "address": "0x28077B47Cd03326De7838926A63699849DD4fa87", "blockNumber": 5158526 },
+    "SpokePool": { "address": "0x13fDac9F9b4777705db45291bbFF3c972c6d1d97", "blockNumber": 5512122 },
     "SpokePoolVerifier": { "address": "0xB4A8d45647445EA9FC3E1058096142390683dBC2", "blockNumber": 5161326 },
     "MulticallHandler": { "address": "0x924a9f036260DdD5808007E1AA95f08eD08aA569", "blockNumber": 5159031 }
   },

package.json

@@ -1,6 +1,6 @@
 {
   "name": "@across-protocol/contracts",
-  "version": "3.0.8",
+  "version": "3.0.9",
   "author": "UMA Team",
   "license": "AGPL-3.0-only",
   "repository": {