new version of mx-chain-comm-go

[miiu96]

Reasoning behind the pull request

• Updated the version of mx-chain-communication-go

Proposed changes

• PR from 'mx-chain-communication-go': Refactor client connection  mx-chain-communication-go#59

Testing procedure

• Check If node with 'HostDriver' enabled is working correctly

Pre-requisites

Based on the Contributing Guidelines the PR author and the reviewers must check the following requirements are met:

• was the PR targeted to the correct branch?
• if this is a larger feature that probably needs more than one PR, is there a feat branch created?
• if this is a feat branch merging, do all satellite projects have a proper tag inside go.mod?

[github-actions]

📊 MultiversX Automated Test Report: View Report

🔄 Build Details:

• mx-chain-go Commit Hash: 4306c57eaa83d6b58d9c59c4d4754b3163ba9bca
• Current Branch: update-mx-chain-communication-go
• mx-chain-go Target Branch: rc/v1.7.next1
• mx-chain-simulator-go Target Branch: rc/v1.7.next1
• mx-chain-testing-suite Target Branch: rc/v1.7.next1

🚀 Environment Variables:

• TIMESTAMP: 21102024-141011
• PYTEST_EXIT_CODE: 0
  🎉 MultiversX CI/CD Workflow Complete!

[gabi-vuls]

Normal allin test: update-mx-chain-communicat-4306c57eaa -> update-mx-chain-communicat-4306c57eaa

--- Specific errors ---

block hash does not match 1854
wrong nonce in block 966
miniblocks does not match 0
num miniblocks does not match 0
miniblock hash does not match 0
block bodies does not match 0
receipts hash missmatch 0

/------/

--- Statistics ---

Nr. of all ERRORS: 2
Nr. of all WARNS: 192
Nr. of new ERRORS: 2
Nr. of new WARNS: 14
Nr. of PANICS: 0

/------/

--- System test go ---

All scenarios from system-test-go are OK!
/------/