feat: Count of launches a validator was involved in

[Matthews3301]

On validator card, there is a number of launches where a validator with this operator address was in.

Uses tx_search RPC endpoint.

Changed "Also validates" to "Validates" as most of validators will have 0 other projects.

[github-actions]

Visit the preview URL for this PR (updated for commit 05928a0):

https://ignite-new--pr68-feat-validator-count-r1aypsxj.web.app

_{(expires Thu, 05 May 2022 13:00:43 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

[fadeev]

I believe this PR will be closing issue 60, so I've linked them.

[fadeev]

Can't verify this is working. For example,

https://ignite-new--pr68-feat-validator-count-r1aypsxj.web.app/projects/30/validators

Says "no validators", but

ignite network chain show validators 30

Shows 1 validator.

I understand that this PR is about validator count, but still. I can see a project where a validator is validating for "1 other project", though.

https://ignite-new--pr68-feat-validator-count-r1aypsxj.web.app/projects/25/validators

Now I want to be able to see 2, 3, etc.

[Matthews3301]

@fadeev Sorry, I should mention, this will only work with validators created since yesterday (27/04/2022) since that's when a new version of CLI was merged and deployed.

[fadeev]

I've created these chains and validators roughly 30 min ago.

[fadeev]

Maybe, I missed something. Please, try publishing 3 chains, apply as a validator (from a different machine, Gitpod is fine), and get requests approved. You should be able to see "validates for 2 other projects".

[Matthews3301]

@fadeev
Problem 1 - validator not showing up even though there's one when using CLI:
I think you're looking at web page for project 30 but CLI is querying campaign 30. This web page is using campaignID 29. CampaignID 30 is being used by project 31.

Problem 2 - your three validators not showing up:
Thank you, good spot. It seems that a validator can be added directly, without submitting a request - when Coordinator account is also a validator. In that case, request_add_validator event will not be created on chain.

I need to rework this entire logic, as per comments in Slack - use a custom new endpoint specifically for this. It should solve problem 2 as well.

[Matthews3301]

Blocked until tendermint/spn#755 resolved.