Expose ValidatorInfo struct

[Stefan-Ethernal]

Description

This PR exposes and utilizes the ValidatorInfo struct. It represents a data transfer object, which is used to hold all validator data retrieved from the smart contract.
Note: It is worth to consider merging it with the ValidatorMetadata object at some point.

Changes include

• Bugfix (non-breaking change that solves an issue)
• Hotfix (change that solves an urgent issue, and requires immediate attention)
• New feature (non-breaking change that adds functionality)
• Breaking change (change that is not backward-compatible and/or changes current functionality)

Checklist

• I have assigned this PR to myself
• I have added at least 1 reviewer
• I have added the relevant labels
• I have updated the official documentation
• I have added sufficient documentation in the code

Testing

• I have tested this code with the official test suite
• I have tested this code manually

[Stefan-Ethernal]

Should it be merged with ValidatorMetadata at some point?

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (feature/v3-parity@bf5ac4d). Click here to learn what that means.
The diff coverage is n/a.

@@                 Coverage Diff                  @@
##             feature/v3-parity    #1162   +/-   ##
====================================================
  Coverage                     ?   54.51%           
====================================================
  Files                        ?      173           
  Lines                        ?    23179           
  Branches                     ?        0           
====================================================
  Hits                         ?    12636           
  Misses                       ?     9545           
  Partials                     ?      998           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[ferranbt]

What is the problem being solved here?

[Stefan-Ethernal]

What is the problem being solved here?

What we want to achieve here is returning an object representation of validator info instead of map (https://github.com/0xPolygon/polygon-edge/pull/1162/files#diff-090d11924b8e0865632ddb3e8da73ceb5b944c6ee26ee8be367f8e626097480aR46), which is more error prone when extracting values and it has some repetitions in code.

So far this was mostly used in e2e tests, so instead of remembering the keys for extracting values for map (https://github.com/0xPolygon/polygon-edge/pull/1162/files#diff-35f7a314332bee5e2f8472071db16a9916b25e85662af4cca846deb81b78800cL635-L636), we already have object representation which is more straight-forward to use.