fix: update p2p metaData file when it is changed

[syjn99]

What type of PR is this?

Bug fix

What does this PR do? Why is it needed?

This PR addresses Issue #13586, where the beacon-chain does not update the metaData file as expected. The issue arises because there is currently no code to write to the metaData file after initialization. As a result, the sequence number stored on disk always remains zero. This behavior is acceptable when the --p2p-static-id flag is not provided. However, it causes significant issues in the P2P processes when a user intends to maintain the same peer ID across sessions. (especially when ping to peers, but those peers found that the sequence number of sender is lower than they manage in their own tables.)

Which issues(s) does this PR fix?

Fixes #13586

Other notes for review

• There is a migration code(migrateFromProtoToSsz) in case user has metaData file already.
• A point of discussion: Should we handle potential errors when the P2P service encounters issues while writing to files? Currently, these errors are ignored. Feedback on this approach would be appreciated.
• I'm afraid that it is common to refer metadata version at phase0 is V1(consensus-specs), but prysm has been referring it as V0.

Acknowledgements

• I have read CONTRIBUTING.md.
• I have made an appropriate entry to CHANGELOG.md.
• I have added a description to this PR with sufficient context for reviewers to understand this PR.

[nalepae]

Thanks for you PR, will look.

[syjn99]

@nalepae
Fixed to save metaData file when p2p service stops.