impl: uploading and retrieving blobs to/from Arweave

[itsyigid]

@virjilakrum Can you revise your work to follow the guidelines provided below, thanks.
You can convert this task to an issue in a repository.

---

The approach we use is like this:

• we create modules that solve a single problem (by modules I mean ES6 modules: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Modules#introducing_an_example)
• if your main goal A requires a sub goal B, create (or get it delegated to someone to create) module B
• each module exports pure functions
• pure functions should always check their inputs and either
  • throw errors (when something should break, let it break) (note that it's not "if it must" but "if it should"!)
  • warn developers by console.warn if something is discouraged but doesn't break the workflow/use case
• for each class or function please add API documentation using the JSDoc format (https://github.com/jsdoc/jsdoc)

I advise you to check out https://git.fybx.dev/fyb/zkl-kds/src/branch/main/key-derivation.js and https://git.fybx.dev/fyb/zkl-kds/src/branch/main/key.js to get an idea on how to develop modules with pure functions.

[virjilakrum]

I'll try to update by the meeting tomorrow, thanks. @fybx

[virjilakrum]

• I've started making updates and modularising the code. There are places I'm stuck, it will be completed when they are fixed. @fybx

Modular Structure:

// file-upload.js
export function uploadFile(file, walletKey) {
  // Implementation
}

// metadata.js
export function createMetadata(name, description, imageUrl, attributes) {
  // Implementation
}

// arweave-transaction.js
export function createAndSignTransaction(data, walletKey) {
  // Implementation
}

// arweave-upload.js
export function uploadToArweave(transaction) {
  // Implementation
}

• It is not easy to move to a more modular and maintainable structure using ES6 modules, pure functions and JSDoc documentation.