* added env-tests to github actions

* removed environmeent

* initial commit

* support for staging network

* run all tests for staging

Co-authored-by: Kevin Jue <kevjue@Kevins-MacBook-Pro.local>

### Description

Surface inflation rate and factor in network:parameters 

### Tested

`celocli network:parameters --node https://forno.celo.org`

<img width="435" alt="Screen Shot 2021-07-09 at 2 49 09 PM" src="https://user-images.githubusercontent.com/3020995/125123949-5ab62e00-e0c5-11eb-9896-3af9d1619ff9.png">

…to 8545 (celo-org#8161)

* Added wsport as configurable. Setting testnet archive wsport default to 8545

* Added FULL_NODES_WS_PORT values

* Blockscout using new websocket endpoint at 8545

### Description

add section for deploying ETH contract to Celo

* add protocol differences

* update to relative links

* changelog added

* versions updated

* keystore added

* chore: resolve to 1.2.3-dev

Co-authored-by: Alex Harley <alexbruceharley@gmail.com>

### Description

This PR updates the the instructions for running a local devchain by referring to the `celo-devchain` package which includes a pre-generated devchain and avoids the need to clone the monorepo and run the migrations.

### Related issues

- Fixes celo-org#6758

* some fixes

* simple test is working

* testing this

* still deciding where the checks should be, need cleanup

* cleaned this up

* lint

* review comments

* lint

* Added prestop hook to fullnode template. Increased baklava memory

* Included new exclusions for prometheus remotewrite and stackdriver for the more frequent unused metrics

* Refined exclusion

* Update prometheus config

* Added encrypted grafana cloud credentials

Co-authored-by: Enrique Ruiz <enrique@keyko.io>

### Description

To enable metrics we had a small bug that get fixed with this PR.


### Tested

Tested in Alfajores

### Description

Fix suggested in [failed CI run](https://app.circleci.com/pipelines/github/celo-org/celo-monorepo/36349/workflows/b03c71a3-61d1-49aa-9d42-fbfbdc3b872d/jobs/476169/parallel-runs/3/steps/3-108) and [slack](https://celo-org.slack.com/archives/CQT5JB2BY/p1626294405043600)

### Tested

CI

### Description

Adds support for Granda Mento on contractkit.

### Other changes

- 

### Tested

Added tests and modified migrations

### Related issues

- Fixes celo-org#7773 

### Backwards compatibility

None

### Documentation

-

* bumps pkg versions

* use new input validation logic

* fix database error metric (drive-by)

* remove timestamp from signer db logic

* sdk changes for using deterministic seed and removing timestamp

* remove timestamp check from combiner

* removes timestamp from combiner getBlindedSig tests

* removes timestamp from signer tests

* updates lockfile

* minor test improvement

* updates lockfile

* fixes error

* bumps contractkit versions in signer and combiner

* Added cEURO to quotes for account validation

* Updated ContractKit in phone-number-privacy package

* Updated Identity dependency in Combiner

* Updated code with PR comments

* Added missing yarn.lock

* Updated logged message in Quote service

* Update yarn.lock

* Update signer dependency

* Update dependencies in combiner

Co-authored-by: Alec Schaefer <alec@cLabs.co>

### Description

Deployment automation for creation, updating, deleting of Celo Rewards Service.

### Other changes

Remove the private key (mnemonic) method for relayer deployment. This was causing deployment issues and we weren't using it.

### Tested

Verified in Alfajores.

### Related issues

- Fixes celo-org#7835 

### Backwards compatibility

Addition of a new micro-service. Does not interfere with existing Komenci services.

### Documentation

N/A

various minor fixes and cleanup noticed during ODIS v1.1.8 deployment and e2e testing

* Add missed variable to enable metrics

* Use the variable

### Description

Fix testnet package if wsPort is 8545 (services cannot have same port defined multiple times)

…org#8320)

### Description

Small refactor to prometheus remote_write due to old approach (using helm `toYaml` funcion) added single quotes to some fields that should not be included in the template.
Also included the encoded variables for grafana cloud in rc1 environment.

### Tested

Deployed to rc1 mainnet cluster.

…rg#8267)

### Description

Fixes contract release process scripts and docs to use simplified tagging scheme

### Tested

CI

### Backwards compatibility

Yes

### Documentation

Smart contract release process docs

### Description

Following up on celo-org#8086, we realized that using mycelo for the tests by default introduces friction for developers making changes to the core contracts, since it requires them to also update the migrations which mycelo uses, which are in the celo-blockchain repo and in Go rather than javascript.  So as a compromise, this PR modifies the tests back to not use mycelo by default.  Instead, they can be switched by devs to use mycelo temporarily (for local runs) as desired, or forced to use mycelo by setting an env variable:

```
export E2E_TESTS_FORCE_USE_MYCELO=true
```

We expect that for the celo-blockchain CI we will set this environment variable, but we won't for the monorepo CI.

### Tested

Verified that the tests now don't use mycelo, but do if you specify the env variable to be true.

### Description

- Adds version logic to ContractKit base wrapper to support generic version gatekeeping

### Other changes

- Modularize and simplify protocol build scripts to only generate artifacts when necessary
- Modify contractkit build:gen script to support targeting contract releases 

### Tested

- Tests added for base wrapper version compatibility

### Related issues

- Fixes celo-org#8018

### Backwards compatibility

Yes

### Documentation

None

### Description

The Twilio Verify Service is a managed service for sending N-digit codes globally. Because there's no risk of sending marketing material, Twilio can automatically manage regulations for each recipient geography on behalf of the sender. The service also manages localization for select markets. We chose Twilio as the first SMS provider to measure the impact of switching to a Verify Service since it 1) is heavily used by many operators 2) supports sending custom codes which minimizes Valora-side changes.

Changes to note:
- Changes SMS text content
  - Android  
    - from `<#> Celo security code is: 12345678 bU9E4ctGtIW` 
    - to `<#>Your Celo verification code is: 12345678 bU9E4ctGtIW`
  - iOS
    - from `Celo security code is: 12345678` 
    - to `Your Celo verification code is: 12345678`
- Expands localized markets from 3 to 36
- Doesn't support a call-back URL which will affect some metrics on our dashboard
- Supporting verification for landlines (using voice)

Pre-requisite steps for Attestation Service operators:
- Create a new Verify Service in the portal
- Create a support ticket to enable custom security codes

### Other changes

We now include `language` and `appSignature` in the `AttestationModel` object. The Verify API uses these directly to adjust the messaging. Added a new migration file for adding these columns to the Attestations table.

Added `twilioVerifySidProvided` to the /status endpoint and tracking via metadata-crawler.

### Tested

Tested manually in Alfajores using Valora Alfajores app:
 - Android device receives app hash and can auto-read message
 - Can re-request SMS from same services
 - Successfully retrieves signature from AS using security code

### Related issues

- Fixes celo-org#8145 

### Backwards compatibility

`AttestationModel` objects that are previously stored in the DB do not have the new properties (`language` and `appSignature). When reading the `AttestationModel`, these new properties are be added for compatibility.

### Documentation

Updated Twilio guide

### Description

Setup RPC_APIs configuration parameter in testnet templates.

Blockscout staging env config

…t libraries (celo-org#8349)

### Description

Current Behavior: Multiple contract libraries have versioning bytecode that is overwritten by inheriting contracts or simply unused
New Behavior: Removed unnecessary versioning in library contracts. Only difference in functionality would be if one were attempt to query the version of a library with getVersionNumber(), although this is seldom done in practice


### Testing
Changes do not need to be tested specifically, since getVersion was not called on libraries.

### Related issues

- Consistently unversion contract libraries celo-org#7435

### Backwards compatibility

Changes are backwards compatible since the functionality being removed was unnecessary and not used.

### Documentation

N/a

### Description

CI doesn't automatically look at new directories, so just moving GrandaMento to the stability directory.

### Other changes

n/a

### Tested

Building & testing

### Related issues

n/a

### Backwards compatibility

Yes

### Documentation

n/a

### Description

See celo-org#5999.

Now that everything is sorted we can safely remove this package (ContractKit lives under packages/sdk).

### Description

This PR aims to make it clearer from the setup instructions that Node.js v12.x must be
used when working with the monorepo.

https://medium.com/celoorg/celo-and-dcent-bringing-greater-access-to-defi-dapps-in-korea-82bb80577b76

…rg#8344)

### Description

Includes fixes for:
* celo-org#8331 (Unclear revert msg for `cancelExchangeProposal`)
* celo-org#8327 (Unfinished & ambiguous comment)

### Other changes

n/a

### Tested

Unit tests

### Related issues

- Fixes celo-org#8331
- Fixes celo-org#8327

### Backwards compatibility

Backward compatible

### Documentation

N/a

celo-org#8362)

* WIP add test for the function without any tz mocking

* add timezone-mock to enable determinist date testing

…ts in the same pod (celo-org#7373)

### Description

Added the threading functionality to the load-test client included in celotool. Included also celotool funcions to help with the fauceting process. The PR includes a complete refactor of the eth load-test functionality, with the most notable changes:

- Added new celotool command `faucet-load-test` to send `CELO` and `cUSD` to any subset of load-test accounts.
- Added new celotool command `prepare-load-test` meant to be run as a init-container for each pod in the load test chart. It setups ethereum accounts and configuration files that will be used by the load-test clients.
- Added multi-threading. Each deployment can be configured with `replicas` (number of pods, each one using a different ethereum client to connect to the client), and `threads` that are different load-test clients inside the same process and sharing the same ethereum client (but using different accounts)

### Tested

Tested extensively in testnets and during performance experiments.


### Related issues

- Fixes celo-org/celo-blockchain#1354

### Backwards compatibility

The changes are isolated to the load-test functionality.

…8191)

### Description

Different deployments with different needs are using the celo-fullnode chart currently. Some of the configuration parameters for this have to be configured chart-wide or env wide (as most variable are not contexted). Following the pattern used in blockscout, this PR adds the capability of adding a custom values.yaml file for each context so we can customize each deployment without adding a lot of env variables for each context. The custom value file has to be `packages/helm-charts/celo-fullnode/{env}-{context}-values.yaml`.

Added two custom values for rc1-gcp-private-txnodes and baklava-gcp-forno-europe-west1 contexts.

### Other changes

No

### Tested

Tested in baklava forno context.

### Related issues

- Fixes #[issue number here]

### Backwards compatibility

No problem

### Documentation

_The set of community facing docs that have been added/modified because of this change_

### Description

_A few sentences describing the overall effects and goals of the pull request's commits.
What is the current behavior, and what is the updated/expected behavior with this PR?_

### Other changes

_Describe any minor or "drive-by" changes here._

### Tested

_An explanation of how the changes were tested or an explanation as to why they don't need to be._

### Related issues

- Fixes #[issue number here]

### Backwards compatibility

_Brief explanation of why these changes are/are not backwards compatible._

### Documentation

_The set of community facing docs that have been added/modified because of this change_

### Description

Addresses celo-org#8330, which calls out that hardcoded min/max values for the veto period would be useful.

* After chatting with Albert, we think there is value in a hardcoded maximum value (set to 4 weeks), but want to preserve the flexibility of being able to set the veto period as low as 0. If down the line the community were to feel that the multisig is not necessary and the `approver` should instead be set to Governance directly, setting the veto period to 0 is desirable. So this PR just adds a `require` enforcing `vetoPeriodSeconds` as <= 4 weeks.
* Apparently there were no existing tests for `setVetoPeriodSeconds`, so they were added

### Other changes

n/a

### Tested

Unit tests

### Related issues

- Fixes celo-org#8330

### Backwards compatibility

Backward compatible

### Documentation

n/a

### Description

* Addresses celo-org#8322 by storing `vetoPeriodSeconds` in each proposal so an active proposal is not affected by a change to the contract's veto period

### Other changes

n/a

### Tested

Unit tests

### Related issues

- Fixes celo-org#8322

### Backwards compatibility

Backward compatible

### Documentation

n/a

remove timezone-mock as its too limited in scope to properly mock (doesnt support Intl or Date.toLocalDateTimeString())
fix some typos

### Description

Updated grafana ingress resource to 1.16+ k8s specification.

* feat: expose blockscout prometheus metrics

* fix: remove spaces that break deployment

Co-authored-by: Donald Hutchison <git@toastymofo.net>

- Revert "GrandaMento - Lock in veto period in proposal - L01 (celo-org#8369)"
- Revert "GrandaMento comment fixes & clearer revert msgs - N01 and N02 (celo-org#8344)"
- Revert "GrandaMento - Add hardcoded max for veto period - L07 (celo-org#8368)"

### Description
- changes metadata-crawler image to `77a392216d4927e85ce4b683508fc0539aa92a34` (includes `Verify API changes`)
- Note: also changes this value in `helm-charts/blockscout/values.yaml` (hasn't been changed in a while, but should be the same image tag referenced I believe)

### Description

I added a few tests to _common_ package of _phone-number-privacy_.

Coverage : 

File                  | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
----------------------|---------|----------|---------|---------|---------------------
All files             |   91.67 |    90.63 |     100 |   91.67 |
 interfaces           |     100 |      100 |     100 |     100 |
  error-utils.ts      |     100 |      100 |     100 |     100 |
  index.ts            |     100 |      100 |     100 |     100 |
 utils                |   88.75 |    89.29 |     100 |   88.75 |
  authentication.ts   |   83.02 |       75 |     100 |   83.02 | 52-55,66-70,128-130
  constants.ts        |     100 |      100 |     100 |     100 |
  input-validation.ts |     100 |      100 |     100 |     100 |

…8476)

* Set ws port to the same as http for blockscout.

* Add default values for sourcify.

* Apply node names to blockscout startup commands.

* Use default route instead of localhost for node name.

* Set full node name in deployments.

* Rename nodeName to erlangNodeName.

* Remove duplicate sourcify.

### Description

docs updated to show that Valora maintains Valora (requested by Denisse [here](https://valora-app.slack.com/archives/CL7BVQPHB/p1628185335065300) )

### Other changes

n/a

### Tested

previewed the rendered page

### Related issues

n/a

### Backwards compatibility

n/a

### Documentation

This page is updated: https://docs.celo.org/getting-started/wallets

…tions. (celo-org#8481)

### Description

A small change made along with @piersy when forno was having some issues. `--txpool.nolocals` is recommended when exposing nodes publicly: ethereum/go-ethereum#18242 (comment).

We noticed it took a really long time for the command to find the most recent block timestamp, which was due to the `transactions.rlp` file being loaded. Adding `--txpool.nolocals` causes that to not be loaded or written to.

I added the `--txpool.nolocals` only for GCP-based full nodes, which I believe are only used for forno (@jcortejoso correct me if I'm wrong or if this will mess other infrastructure up that I'm not familiar with).

### Other changes

n/a

### Tested

Deployed forno full nodes

### Related issues

n/a

### Backwards compatibility

backward compatible

### Documentation

n/a

The timeout was increased to 600 to overcome the time taken to process
the txpool local txs, but due to the addition of the -txpool.nolocals
flag that extended timeout is no longer required.

### Description

Upgrade eksportisto to the latest version which includes this PR:
- celo-org/eksportisto#58

### Description

Enabled blockscout metrics by default.

### Other changes

Increased the connection pool size.

### Tested

Tested on all envs.

### Backwards compatibility

Yes.

* Separate testnet from production decryption permissions

* Remove debug msg

### Description

This includes:
* An env test for GrandaMento that tests selling and buying CELO for: (1) creating & immediately cancelling an exchange proposal and (2) creating and executing an exchange proposal.
* Small refactor of env-tests to use contractkit's `StableToken` & related functions for stable token specific things
* Added CELO fauceting in env-tests
* Some small changes to the GrandaMento contractkit wrapper
* Added stable token exchange limits to the GrandaMento migrations

### Other changes

* Small fix to testnet helm chart

### Tested

Ran against a testnet I created

### Related issues

- Fixes celo-org#8065 

### Backwards compatibility

They are backward compatible

### Documentation

n/a

### Description

This version is already deployed. Just updating our env files to reflect it.

### Description

Merge audit fixes triaged in https://github.com/celo-org/celo-monorepo/projects/2

### Tested

CI

### Related issues

- Fixes celo-org#8437

### Backwards compatibility

Yes

### Documentation

_The set of community facing docs that have been added/modified because of this change_

### Description

Accounts can now query matchmaking unlimited times as long as they use the same phone number and provide a DEK signature of that phone number in the request

### Other changes

Adds DB migration instructions to Combiner and Signer READMEs

Adds functionality for e2e tests to bypass verification check in combiner on alfajores when using specific fake phone numbers

Adds `yarn update-dependency-graph` command to root package.json

Adds documentation on ODIS replay handling for both signing and matchmaking

Updates auto generated ODIS docs

Factors DEK signature verification into its own function in common package

Adds custom `seed` parameter to blinding client in `@celo/identity`

Adds custom `blindingFactor` parameter to `getPhoneNumberIdentifier` in  `@celo/identity`

Adds `dekSigner` parameter to `getContactMatches` in  `@celo/identity`

### Tested

Unit and e2e tests

### Related issues

- Fixes https://app.zenhub.com/workspaces/cap-sprint-board-60059934ed9c6f000e5594f6/issues/celo-org/celo-monorepo/8312

### Backwards compatibility

Yes

### Documentation

Updated in PR

* doc: Update foundation voting policy

* Update celo-foundation-voting-policy.md

### Description

Adds error handling to flake tracker so that CI doesn't fail if there's an issue

### Other changes

None

### Tested

In CI 

### Related issues

- Fixes CI blocker

### Backwards compatibility

Yes

### Documentation

None

…-org#8537)

### Description

- Handles unregistered contracts in governance tooling
- Adds `--afterExecuting{ID|Proposal}` to `governance build:proposal` for batching support

### Other changes

- Unify unregistered contracts handling in sdk

### Tested

against staging
`./bin/run governance:show --node http://localhost:8545 --proposalID 19`

```yaml
proposal:
  0:
    contract: Registry
    function: setAddressFor
    args:
      0: GrandaMento
      1: 0xF9F8bfFB41883A0a224400C2CA3Aa629ae8156DC
    params:
      identifier: GrandaMento
      addr: 0xF9F8bfFB41883A0a224400C2CA3Aa629ae8156DC
    value: 0
  1:
    contract: GrandaMentoProxy
    function: _setAndInitializeImplementation
    args:
      0: 0xFA5696a00b612f23386fE0a58AdccB78c76012Fc
      1: 0xd13f90b4000000000000000000000000000000000000000000000000000000000000ce100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003f870857a3e0e380000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000127500
    params:
      implementation: 0xFA5696a00b612f23386fE0a58AdccB78c76012Fc
      callbackData: 0xd13f90b4000000000000000000000000000000000000000000000000000000000000ce100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000003f870857a3e0e380000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000127500
      initialize@d13f90b4:
        _registry: 0x000000000000000000000000000000000000ce10
        _approver: 0x0000000000000000000000000000000000000000
        _maxApprovalExchangeRateChange: 300000000000000000000000
        _spread: 0
        _vetoPeriodSeconds: 1209600
    value: 0
```

`./bin/run governance:build-proposal --node http://localhost:8545 --output test.json --afterExecutingID 19`

```
After executing provided proposal, account for registry remappings: {
  "GrandaMento": "0xF9F8bfFB41883A0a224400C2CA3Aa629ae8156DC"
}
Transaction #1:
? Celo Contract: GrandaMento
? GrandaMento Function: setStableTokenExchangeLimits
? stableTokenRegistryId: StableTokenEUR
? minExchangeAmount: 100
? maxExchangeAmount: 10000
Transaction #2:
? Celo Contract: ✔ done
Outputting proposal to test.json
Simulating proposal execution
```

### Description

- Bump versions of WalletConnect libraries
- CAIP10/50/short-name address parsing

### Other changes

N/A

### Tested

Unit and E2E tests

### Related issues

N/A

### Backwards compatibility

N/A

### Documentation

N/A

This reverts commit 1f3780d.

### Description
Small fixes or the loadtest in networks deployed with mycelo

…org#8581)

### Description

Defines scale up and scale down behavior for blockscout API HPA.
Scales up if the average CPU usage is higher than the defined threshold (currently 70%), doubling the number of pods or adding 2 pods every 30 seconds whichever affects the higher number of pods.
Scales down after 10 minutes removing 20% of pods or 1 pod every minute whichever affects the smaller number of pods.

### Tested

Tested on staging.

### Documentation

https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/#support-for-configurable-scaling-behavior

### Description

As described in celo-org#7774

### Other changes

- Generalized functions on contractkit to be used for the cli testing as well

### Tested

Added unit tests.

### Related issues

- Fixes celo-org#7774

### Backwards compatibility

-

### Documentation

- Added, auto generated.

Also point all three networks (baklava, alfajores and mainnet) to the
same container registry.

* add testing documentation to protocol readme

* refactor epoch time travel

* extensive adjustment factor testing

* add tests and fix total supply & reserve initialisation numbers

* remove test-utils.ts changes

* update epoch rewards init parameters

* refactor test init

* Update packages/protocol/test/governance/network/epochrewards.ts

Co-authored-by: Roman Croessmann <42186452+rcroessmann@users.noreply.github.com>

* fix typo

* add one year tests

* reframe 'year' to '365 epochs'

* work in lint feedback

Co-authored-by: Roman Croessmann <42186452+rcroessmann@users.noreply.github.com>
Co-authored-by: Nelson Taveras <nelson@clabs.co>

…elo-org#8257)

* Incorporate js keystore into attestation service with backwards compatibility

* Include keystores in package.json

* Fix linting error

* PR fixes

* Update dependency graph

* Copy keystores package into AS dockerfile

* Update attestation service deployment docs (celo-org#8264)

* Update attestation service deployment docs

* Wording suggestion (PR review)

Co-authored-by: Cody Born <codyborn@outlook.com>

* Nit wording

* Fix instructions around starting AS docker container

* Correct old typo

* Add forno to docs

* Clarify submission vs reading from chain

* Tiny rephrase

* Docs fixes for single celo provider method

* Fix link and rephrase

Co-authored-by: Cody Born <codyborn@outlook.com>

* Implement fallback on error only

* wip

* Implement just-in-time prioritization

* Simplify selection logic

* Use isYes for env var processing

* Add timeout handling but wip

* Clean up kit init logic

* wip: implementation working

* Fixed bug and added periodic edge case check

* Clean up some constants from init

* Remove console logs and add one log statement

* Update env variables

* Fix typo

* Fix lint checks

* Use timeout instead of withTimeout

* Update package version pre-testing

* Update docs

* Update helm charts and celotool for deployment with backup provider

* wip includes deployment image hash

* Fix linting

* Update packages/attestation-service/src/db.ts

Co-authored-by: Cody Born <codyborn@outlook.com>

* Add docstrings to initializeKits and execWithFallback

* Update image tag to latest 1.4.0-dev build

Co-authored-by: Cody Born <codyborn@outlook.com>

### Description
Added two new pages with instructions to connect a Ledger device to Celo Web Wallet & Celo Terminal

### Description

We saw some errors in the Combiner logs that indicated that their weren't enough instances allocated; despite very low traffic. Setting a min instance count to prevent minor spikes in traffic from not being served.

> The request was aborted because there was no available instance


### Tested

Testing in staging before merging.

### Backwards compatibility

Yes.

### Documentation

N/A

Adding back doc updates lost in revert. Using MetaMask with Celo updates to clarify warnings and tutorial language.

### Description

We're deprecating the old encryption key (`github-key`) to replace with a new one that is environment specific (prod vs non-prod).

### Tested

Encrypted/Decrypted using the new key

### Related issues

- Fixes celo-org#8542 

### Backwards compatibility

Updating .enc files so the old key is no longer necessary

…ds (celo-org#8587)

* Add annotation with information about deployment for grafana dashboards

* Config as environment variables

* Fix end lines

* Fix comments

### Description

Error message in DB is max of 255 chars and throws the following exception when the error is longer than this:
`value too long for type character varying(255)`

This prevents retries during failure since this breaks out of the retry loop.

### Tested

Tested with a single attestation service for a week. Verified no errors of this type came through.

### Related issues

- Fixes #[issue number here]

### Backwards compatibility

Yes.

### Documentation

N/A

* update signer dependency

* Added fallback for signers.

* Added test and options to Circuit Breaker

* Removed console.log

* Added circuit breaker for every signer

* Corrected import in Combiner

…celo-org#8550)

### Description

This was needed to create the GrandaMento "activation" governance proposal on staging while CR5 (the proposal that would set GrandaMento in the registry & initialize the contract) was not executed yet.

* Brings out the `--afterExecutingProposal` and `--afterExecutingID` logic from `governance:build-proposal` and reuses it in `governance:propose`
* Allows registry additions to be passed into `proposalToJSON`

### Other changes

n/a

### Tested

Was able to propose the GrandaMento activation governance proposal with the use of `--afterExecutingID`

### Related issues

n/a

### Backwards compatibility

Fully backward compatible

### Documentation

Doc changes autogenerated

… yet registered (celo-org#8569)

### Description

Fixes fetching network parameters when some sdk contracts are unregistered as followup to celo-org#8537

### Tested

<img width="555" alt="Screen Shot 2021-08-30 at 8 00 45 PM" src="https://user-images.githubusercontent.com/3020995/131434692-d9d9f613-a7ac-4cad-97cd-65f6a7940c57.png">

…lo-org#8607)

### Description

Simplifies container deployment and should remove an issue we occasionally saw when the genesis block was incorrect in GCS. Runs the geth node in the updated, post-donut way.

### Other changes
- updates the release process alfajores deployment slightly (+ docs to reflect that), to make it more consistent with baklava + mainnet release tagging. With these slight changes, we would try to ensure that `attestation-service-alfajores` reflects the candidate release version that is currently deployed on alfajores, and can test + make changes to this before tagging the official release on GitHub. (`attestation-service-baklava` is already supposed to, so this would also make the two tags consistent + the one that we deploy)
(- did not change this but maybe we should revisit whether we want to remove the baklava release section if that is no longer part of the process?)
- bumped AS version to `1.4.0` (from `1.4.0-dev`...I can separate this into its own PR if this clutters this PR too much, but that feels like overkill since this the AS as is should be the 1.4.0 release candidate 😅)

### Tested
- tested deployment, checked container logs to make sure startup worked as expected and that the geth ultralight client syncs properly (there is one "db already initialized" error in the logs @codyborn but does not block proper functioning afterwards; this is the case with/without the new deployment changes)

### Related issues

- Fixes celo-org#8460
- Related to celo-org#8244

### Description

Add author in grafana release annotation

* update signer dependency

* Added fallback for signers.

* Added test and options to Circuit Breaker

* Removed console.log

* Added circuit breaker for every signer

* Corrected import in Combiner

* Added tests

* Added working package.json for new tests

* remove the 'd' package

* Change yarn lock

### Description

Based on observation from monitoring:
- decreases CPU requests for db proxy container for indexer, web and api.
- increases CPU requests for api and web, and triples the connection pool size per pod, at the same time halving the max number of replicas in each HPA.

### Description

This PR adds a Certora spec for the Reserve contract, so far with one rule: checking that the Reserve's funds cannot be moved by an address that's not an approved spender.

### Other changes

* Added this as a CI job
* Set all spec-related scripts as executable

### Tested

Spec passes when running locally

### Related issues

- Fixes celo-org#8513