test(e2e): add connector bytecode update admin test

[lumtis]

Description

Add an admin test testing ZEVM connector bytecode update

Closes: #1999

Execution example: https://github.com/zeta-chain/node/actions/runs/8644743022/job/23700500386
(the liquidity cap test fails, issue tracked for this one)

[github-actions]

!!!WARNING!!!
nosec detected in the following files: e2e/e2etests/test_update_bytecode_zrc20.go

Be very careful about using #nosec in code. It can be a quick way to suppress security warnings and move forward with development, it should be employed with caution. Suppressing warnings with #nosec can hide potentially serious vulnerabilities. Only use #nosec when you're absolutely certain that the security issue is either a false positive or has been mitigated in another way.

Only suppress a single rule (or a specific set of rules) within a section of code, while continuing to scan for other problems. To do this, you can list the rule(s) to be suppressed within the #nosec annotation, e.g: /* #nosec G401 */ or //#nosec G201 G202 G203
Broad #nosec annotations should be avoided, as they can hide other vulnerabilities. The CI will block you from merging this PR until you remove #nosec annotations that do not target specific rules.

Pay extra attention to the way #nosec is being used in the files listed above.

[ws4charlie]

lgtm