Refactor and improve deweb code

Nobody has claimed this yet.

A lot of code is duplicate among deweb CLI and deweb frontens (home and uploader)

This lead to unmaintainable code and block further improvements.

what to do:

- add e2e test in the CLI to test differents usecase: website add/update/delete, with metadatas, file metadata etc..
this will allow us to improve the code with confidence. If the same code is used in cli and frontend, its a win
- Put contracts specific code in massa web3 and reuse the the code in cli and frontends
- indexer contract
- retrieve stored websites, add a website
- website contracts
- get website data, metadatas
- create a generic operation batch sender that will be used for website chunk upload
- this is a important piece of code, we need a clean and reliable stuff that we can optimize
- It should use the sendOperationS (with a S) endpoint of the node.
- Investigate how it could work with wallet provider and the supported wallets (sub issues will probably needed here)

- Eventually create a Deweb folder in massa web3 that will gather the Deweb specific helpers

Start by mapping the duplicated code across the deweb CLI and frontend areas, then review the requested CLI end-to-end cases for website add, update, delete, and metadata handling. Define completion around shared Massa web3 contract helpers, a generic batch sender using the sendOperationS endpoint, and passing coverage for those workflows.

Written by the indexing model from the issue text.