Add smesher id to grpc reward object

[piersy]

Motivation

Closes - #4529

Changes

Adds the smesher ID into the reward responses from the AccountDataStream and GlobalStateStream. Notably this does not add the smesher ID into the reward responses from the AccountDataQuery endpoint because that loads rewards from the DB and currently the DB does not record the smesher ID.

Questions

This work was to allow the explorer to display rewards by smesher ID, the explorer can use this branch for now, does it make sense to merge this for everyone else before doing the work to migrate the DB?

On the flipside, will it cause problems having to maintain a fork for the explorer?

Test Plan

Updated the unit tests for the affected services

DevOps Notes

• This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
• This PR does not affect public APIs
• This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
• This PR does not make changes to log messages (which monitoring infrastructure may rely on)

[codecov]

Codecov Report

Merging #4850 (7179380) into develop (21c602e) will increase coverage by 76.9%.
The diff coverage is 100.0%.

❗ Current head 7179380 differs from pull request most recent head 7890737. Consider uploading reports for the commit 7890737 to get more accurate results

@@            Coverage Diff             @@
##           develop   #4850      +/-   ##
==========================================
+ Coverage         0   76.9%   +76.9%     
==========================================
  Files            0     261     +261     
  Lines            0   29728   +29728     
==========================================
+ Hits             0   22863   +22863     
- Misses           0    5416    +5416     
- Partials         0    1449    +1449     

Files	Coverage Δ
api/grpcserver/globalstate_service.go	70.2% <100.0%> (ø)
common/types/block.go	65.0% <ø> (ø)
events/reporter.go	64.5% <ø> (ø)
genvm/vm.go	79.8% <100.0%> (ø)
mesh/executor.go	80.1% <100.0%> (ø)

... and 256 files with indirect coverage changes