Refactor code in web3 tests

[filev94]

Problem

A lot of tests have similar individual setup that can be extracted in a parent class and thus making the code easier to read and maintain. Methods like persistFungibleToken and fungibleTokenPersist exist in child and parent classes that are duplicated in different suits and mistake in one needs to be corrected in all. This will remove the need to fix broken tests individually

Solution

• Add general "setup" methods in AbstractContractCallServiceTest that child classes can use to setup the test (accountPersist, accountPersistWithAlias, fungibleToken, etc)
• Add customizable methods (that accept Supplier) in AbstractContractCallServiceTest that child classes can use when there is a small difference in setup of a test
  If this can be done with 1 method that serves both purposes - best.

Alternatives

No response

[filev94]

This issue mentioned here SENDER_ALIAS_ SENDER_PUBLIC_KEY will be fixed in future PR

[filev94]

The issue mentioned here persistFungibleToken() will be fixed in a future PR, so that the latter does not become big.

[filev94]

The issue mentioned here will be addressed in a future PR