Allow upgrading WASM blobs

[ra0x3]

• Per the comment here
• Previously Add mechanism to upload indexer module. #41
• Allow users to upload new WASM blobs

Additional context

• Might be able to be done via some web endpoint?
• Should ideally happen with little-to-no downtime

[ra0x3]

@tjsharp1

• This sounds like something that is ready for work?

• I feel like New sqlite support #134 might have to go in before this could start 🤔 (could always just branch off of your work)

• But yea any thoughts here? I'm thinking this functionality will:

  • Receive a blob at some endpoint POST - /wasm
  • Validate the blob received is the blob sent
  • Store the blob on disk wherever the previous module is stored
    • Either overwrite the pre-existing blob or deprecate it
  • Call some function to add a new indexer using a new manifest containing the new module (same functionality as here) -- which will/should overwrite the old indexer which was using the old manifest

• Per your comment in the block explorer issue I'm thinking we leave authentication out for now (will be super easy to add later)

• We could also maybe track WASM updates via some metadata table (sort've how we track table metadata with the graph registry)