feat(reliable-integration): update peer metadata schema

[glevco]

Motivation

Our reliable integration use case (wallet service) suggested that the peer_id attribute could be moved on the event schema, and also that network should be included.

Acceptance Criteria

• Move peer_id upwards in the event schema.
• Add network to the event schema.

Checklist

• If you are requesting a merge into master, confirm this code is production-ready and can be included in future releases as soon as it gets merged

[codecov]

Codecov Report

Attention: 5 lines in your changes are missing coverage. Please review.

Comparison is base (ab1a6ca) 84.63% compared to head (5a0a15a) 84.59%.
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #804      +/-   ##
==========================================
- Coverage   84.63%   84.59%   -0.04%     
==========================================
  Files         270      271       +1     
  Lines       22290    22311      +21     
  Branches     3404     3406       +2     
==========================================
+ Hits        18865    18874       +9     
- Misses       2757     2768      +11     
- Partials      668      669       +1     

Files	Coverage Δ
hathor/builder/builder.py	91.30% <100.00%> (+0.04%)	⬆️
hathor/builder/cli_builder.py	74.48% <100.00%> (ø)
hathor/event/event_manager.py	91.60% <ø> (ø)
hathor/event/model/base_event.py	100.00% <ø> (ø)
hathor/event/websocket/factory.py	93.33% <100.00%> (+0.22%)	⬆️
hathor/event/websocket/response.py	100.00% <100.00%> (ø)
hathor/feature_activation/bit_signaling_service.py	85.24% <ø> (ø)
hathor/manager.py	80.73% <100.00%> (ø)
hathor/transaction/storage/transaction_storage.py	93.04% <100.00%> (ø)
...ions/add_feature_activation_bit_counts_metadata.py	68.75% <68.75%> (ø)

... and 4 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.