feat: make ci ✅ with 💚 and 🥑s

[bowd]

Description

• Split jobs for better readability
• Make storage checks run only on push to develop (i.e. not for each commit of a work in progress branch) in an attempt to not hit rate limits.
• removed the slither.db.json and inlined ignores - it's important to actually review these and see if we want to actually fix any of them
• made slither ignore contracts/common and contracts/legacy . Common will be moved to @celo/contracts npm dependency anyway.
• fixed echidna compilation issue, yey!

Other changes

• Moved SortedOracles.sol to common because moving forward that contract will be owned by clabs and we will need to deploy it through their pipeline. So everything in common will move to @celo/contracts, including SortedOracles.

Tested

In progress

Related issues

N/A

Backwards compatibility

N/A

Documentation

N/A

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[openzeppelin-code]

feat: make ci ✅ with 💚 and 🥑s

Generated at commit: b2efe93a6788e73acb51e9b94b9c527e429b4024

🚨 Report Summary

	Severity Level	Results
Contracts	Critical High Medium Low Note Total	3 3 0 13 38 57
Dependencies	Critical High Medium Low Note Total	0 0 0 0 0 0

---

For more details view the full report in OpenZeppelin Code Inspector

[chapati23]

CI is greeeeeeeen 🤩🤩🤩

lgtm, just some questions/suggestions

[bowd]

@philipraetsch thanks for the suggestions!
I've updated the foundry version and removed the build steps from slither.
We still need the build step in echidna because they haven't update echidna-action to install Foundry in the docker. They did update slither-action tho' so if anybody wants to be a good samaritan you can open a PR there :)

[baroooo]

I believe we can disable timestamp matcher at the config level. Because,
1- I don't think we rely on it at a critical level
2- Not sure about specifics of Celo, but it is much harder to exploit in a PoS setup
3- Timestamps are used frequently in our repo

The rest looks good as it is.