Update Web3j dependencies

[fab-10]

PR description

Compilation is failing due some web3j artifacts not available anymore, so just updating them to latest verison

A problem occurred configuring project ':acceptance-tests:tests'.
> Could not resolve all files for configuration ':acceptance-tests:tests:classpath'.
   > Could not resolve org.web3j:web3j-gradle-plugin:4.9.2.
     Required by:
         project :acceptance-tests:tests > org.web3j:org.web3j.gradle.plugin:4.9.2
      > Skipped due to earlier error
   > Could not resolve org.web3j.solidity:solidity-gradle-plugin:0.3.5.
     Required by:
         project :acceptance-tests:tests > org.web3j.solidity:org.web3j.solidity.gradle.plugin:0.3.5
      > Skipped due to earlier error

Fixed Issue(s)

Thanks for sending a pull request! Have you done the following?

• Checked out our contribution guidelines?
• Considered documentation and added the doc-change-required label to this PR if updates are required.
• Considered the changelog and included an update if required.
• For database changes (e.g. KeyValueSegmentIdentifier) considered compatibility and performed forwards and backwards compatibility tests

Locally, you can run these tests to catch failures early:

• unit tests: ./gradlew build
• acceptance tests: ./gradlew acceptanceTest
• integration tests: ./gradlew integrationTest
• reference tests: ./gradlew ethereum:referenceTests:referenceTests

[shemnon]

Is this needed? There are no plugins from the tech.pegasys namespace.

[fab-10]

it is needed because new web3j plugin has tech.pegasys:jc-kzg-4844 as dependency

[shemnon]

That's not good. Web3j cannot be loaded entirely from maven central? Consensys should invest time in getting these published to Maven Central.

[fab-10]

I know someone is already working on that, so this will not be required in a future version, in the meantime what you prefer, using version 4.10.0 of the plugin or temporarily keeping the extra repo here?

[shemnon]

We do have the repository in our general listings. I was hoping we could keep the plugins section minimal. So this is acceptable since a long term solution is progressing.