fix linter in tests

[AdoAdoAdo]

Reasoning behind the pull request

Proposed changes

Testing procedure

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?

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 76.62%. Comparing base (e1698c7) to head (adf0114).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #7859   +/-   ##
=======================================
  Coverage   76.62%   76.62%           
=======================================
  Files         814      814           
  Lines      110955   110955           
=======================================
+ Hits        85014    85019    +5     
+ Misses      20146    20142    -4     
+ Partials     5795     5794    -1     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[github-actions]

❌ Integration Tests completed with failures or errors.

📊 MultiversX Automated Test Report: View Report

🔄 Build Details:

• mx-chain-go Commit Hash: adf0114a3090dfacc2eb9c3a0cc86124f203d3c4
• Current Branch: fix-linter-merge
• mx-chain-go Target Branch: master
• mx-chain-simulator-go Target Branch: main
• mx-chain-testing-suite Target Branch: main
• mx-chain-simulator-go Commit Hash: 771e2f48f7a5d3cc83fc880558e5efe7befd7ee8

🚀 Environment Variables:

• TIMESTAMP: 2026_MAY_27__14_53_31
• PYTEST_EXIT_CODE: 1