Remove sub-dockerfiles and sub-contracts

[rzadp]

Purpose

The purpose of this PR is to:

• Remove dependency on package-lock.json and get rid of excessive Dockerfiles as per Remove dependency on package-lock.json in Dockerfiles #44
• Migrate into common contracts in root directory instead of nested submodules and git clones in sub-Dockerfiles as per Extract repeated submodules/poa-bridge-contracts into one in root dir #21

Achieved work

• oracle-e2e and ui-e2e share parity config in root directory
• oracle-e2e uses contracts in root directory
• ui-e2e uses contracts in root directory
• Reduced number of Dockerfiles
• Made ui-e2e work on CI - closes Extract bridge-ui/e2e and configure CircleCI #6

Contracts issues

• contracts/package.json is installed by yarn and included in yarn workspaces, but contracts/deploy/package.json is installed separately by npm
  • yarn does not allow nested package.json's
• There are contracts-2.1.0 and contracts-2.2.0 because oracle-e2e and ui-e2e were hardcoded to use these tags and do not work with our contracts at 2.3.0-rc0
  • Created Update ui-e2e to work with contracts at 2.3.0-rc0 #52 and Update oracle-e2e to work with contracts at 2.3.0-rc0 #53 to fix this, then we can remove contracts-* and Extract repeated submodules/poa-bridge-contracts into one in root dir #21 can be completely finished
  • yarn workspaces don't work with sub-folders of the same name poa-parity-bridge-contracts, so the excessive sub-folders are handled by npm

[akolotov]

@patitonar please take a look as well

[akolotov]

@patitonar do you have understanding why the e2e on UI side does not work with the contracts v2.2.0? I see that the difference between v2.1.0 and v2.2.0 is almost nothing from the UI point of view.

[rzadp]

@patitonar do you have understanding why the e2e on UI side does not work with the contracts v2.2.0? I see that the difference between v2.1.0 and v2.2.0 is almost nothing from the UI point of view.

I didn't spend time to look into this yesterday as I wanted to roll out the PR for review sooner. Maybe I'll be able to figure this out today.

[akolotov]

@patitonar do you have understanding why the e2e on UI side does not work with the contracts v2.2.0? I see that the difference between v2.1.0 and v2.2.0 is almost nothing from the UI point of view.

I didn't spend time to look into this yesterday as I wanted to roll out the PR for review sooner. Maybe I'll be able to figure this out today.

I think I found the difference. The following must be updated in ui-e2e/envs/contracts.env, ui-e2e/envs/erc-contracts.env, ui-e2e/envs/erc-native-contracts.env:

• DEPLOYMENT_GAS_LIMIT=5000000
• HOME_OWNER_MULTISIG, HOME_UPGRADEABLE_ADMIN_VALIDATORS, HOME_UPGRADEABLE_ADMIN_BRIDGE must be updated to HOME_BRIDGE_OWNER, HOME_VALIDATORS_OWNER and HOME_UPGRADEABLE_ADMIN
• FOREIGN_OWNER_MULTISIG, FOREIGN_UPGRADEABLE_ADMIN_VALIDATORS, FOREIGN_UPGRADEABLE_ADMIN_BRIDGE must be updated to FOREIGN_BRIDGE_OWNER, FOREIGN_VALIDATORS_OWNER, FOREIGN_UPGRADEABLE_ADMIN

After that the contracts v2.2.0 should work for both set of e2e tests.

[patitonar]

oracle-e2e and ui-e2e should be able to work with 2.3.0-rc0. The reason is that there are some .env variables that need to be added/updated.

Some of these variables probably need to be added in some on the env files and some on others env files:

DEPLOYMENT_GAS_LIMIT_EXTRA=0.2
HOME_REWARDABLE=false
FOREIGN_REWARDABLE=false
VALIDATORS_REWARD_ACCOUNTS=0x0000000000000000000000000000000000000000
DEPLOY_REWARDABLE_TOKEN=false
ERC20_EXTENDED_BY_ERC677=false
BLOCK_REWARD_ADDRESS=0x0000000000000000000000000000000000000000
DPOS_STAKING_ADDRESS=0x0000000000000000000000000000000000000000

[akolotov]

Please remove duplicated DEPLOYMENT_GAS_LIMIT parameter in the files located in ui-e2e/envs

[akolotov]

@patitonar could you check one more time and approve the PR? thanks!