e2e: skip setting EVM networks on nodes in nonEVM e2e tests

[aalu1418]

Current e2e tests add EVM networks to nonEVM test runs. And by adding EVM networks it overrides any previous changes to the base config related to EVM networks.

Using EVM networks on nonEVM runs leads to flakes because the EVM networks may not respond in time and the nodes will throw unrelated error logs for EVM issues in a nonEVM e2e test.

Requires Dependencies

• e2e: bump integration-test version with nonEVM handling chainlink-solana#779

[github-actions]

I see you updated files related to core. Please run pnpm changeset in the root directory to add a changeset as well as in the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

🎖️ No JIRA issue number found - Please include it in the PR title or in a commit message.

[cl-sonarqube-production]

Quality Gate failed

Failed conditions
108.89% Technical Debt Ratio on New Code (required ≤ 4%)
E Maintainability Rating on New Code (required ≥ A)

See analysis details on SonarQube

Catch issues before they fail your Quality Gate with our IDE extension SonarLint