feat: add validators voting data to db

[pdp2121]

High Level Overview of Change

On every most recent flag ledger, store for each validator into ballot table:

• ledger index - this will allow us to keep the most recent vote for a validator incase we missed the most recent flag ledger.

• fee voting

• amendment voting

This is to get amendment voting status and later fee votes.

Type of Change

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Refactor (non-breaking change that only restructures code)
• [ ] Tests (You added tests for code that already exists, or your new feature included in this PR)
• [ ] Documentation Updates
• [ ] Release

Future Tasks

• Add voting data to validators endpoint.
• Add a new amendments endpoint to returns amendments enabled on a network and voting data for pending ones.

[pdp2121]

I will continue to monitor the code locally (looked good till now). Pushed this to get some feedback.

[pdp2121]

There needs to be an API endpoint to access this data

Yes, that would be the upcoming PR. We separated this into smaller tasks

[intelliot]

There needs to be an API endpoint to access this data

Yes, that would be the upcoming PR. We separated this into smaller tasks

That's good, but you should note this in the "Future Tasks" section of the PR description template.

[pdp2121]

There needs to be an API endpoint to access this data

Yes, that would be the upcoming PR. We separated this into smaller tasks

That's good, but you should note this in the "Future Tasks" section of the PR description template.

I have updated the description to include future tasks. Thanks Elliot!

[pdp2121]

@mvadari @ckniffen I have added fee data for validators that do not vote for a fee changed in the latest commit. Please let me know if it looks good, then we can test on staging