feat: steward report card

#### Decription

The task here would be to tweak out Stewards model to also be able to store the following data.

| Data | Info | Data Source / API | Can be auto updates |
|----------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------|---------------------|
| GTC delegated so far | Same info as

https://www.withtally.com/governance/gitcoin/voters | | Y |
| Votes casted by steward on Snapshot | Snapshot API | | Y |
| Proposals create by steward on Snapshot | Snapshot API | | Y |
| Number of posts created by delegate on https://gov.gitcoin.co/ | Posts Count in

- https://gov.gitcoin.co/c/governance-meta/6
- https://gov.gitcoin.co/c/workstream-discussion/9
- https://gov.gitcoin.co/c/governance-proposals/5 | | Y |
| Number of comments made by delegate on https://gov.gitcoin.co/ | Comment > 100 chars should be counted in

- https://gov.gitcoin.co/c/governance-meta/6
- https://gov.gitcoin.co/c/workstream-discussion/9
- https://gov.gitcoin.co/c/governance-proposals/5 | | Y |
| Which workstreams do the steward lead | - Use badges to depict if steward leads a workstream
- Manually added by admin (for now) | | |
| Key actions taken by steward | This will be manual entered (via steward/admin ) | | |
| Grants (amount + count ) made by steward | | Stored in DB | Y |
| Coordinape score | THIS IS NOT READY YET | | ? |
| Steward Bio / Name / handle / address | This is data we collect while ingesting a steward. We already have this in our DB | Stored in DB | N | | Stored in DB | N |

**Things to consider**

- These need to run via a cron
- Decide which Data should be available locally and which should be fetched

**Nice to have**

- track how delegation varies over time for a steward
- key actions taken by steward

**Things to explore**

- check out how stewards are voted in mirror dao

_Note: this would have a frontend but that would be tracked separately. We'd want the backend API ready to provide this info whenever the frontend is built out_