Refactor hardcoded id of system account in web3 tests

[filev94]

Description:
This PR refactors the hardcoded id of 700 for system account and instead generates one between 1 to 750 inclusive with the exception of 2 and 98 which i found to be special ids.

Related issue(s):

Fixes #10407

Notes for reviewer:

Checklist

• Documented (Code comments, README, etc.)
• Tested (unit, integration, etc.)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

[kselveliev]

I just checked how the domainBuilder.id() method works and it is the following.

 /**
     * Generates an encoded entity id above the max reserved id 1000. Use {@link #number()} instead for a number
     * starting from 1.
     *
     * @return The generated encoded entity id.
     */
    public long id() {
        return id.incrementAndGet() + LAST_RESERVED_ID;
    }

Looks like the domainBuilder auto generates ids but from 1000 -> upwards, so we shouldn't really be concerned about collisions if our custom id is below 1000. I'm pretty confident thats the case. So we might even close the PR without making any changes to this since it probably isn't a problem

[filev94]

@bilyana-gospodinova, please share your opinion on the case - if we should continue with the change or close the PR.

[bilyana-gospodinova]

I double checked and I think Kris is right - the automatic ids that the domain builder generates start from 1000, so there shouldn't be a case where a collision might occur (which was the issue that we were trying to fix).

[filev94]

Closing this PR as per comment regarding the domainBuilder ids. Change is not needed.