VOD upload process is ambiguous

[insanity54]

I have a checklist for uploading vods. I suppose it's not completely ambiguous, but it's something that only I understand. I want to change the upload flow to something that anybody can use and understand.

The first step is an upload endpoint in the website where authed users can upload VODs. This step should require some barebones metadata including date, announceUrl, and optionally a note to the db admin.

• [x] GET /upload
• [x] save VOD to B2
• [x] populate videoSrc in db

Once the VOD is created in Strapi, an admin must approve/publish the vod. After which, futureporn-qa carries out the following tasks

• [x] listens for a publish webhook
• [x] downloads videoSrcB2 => localPathVideoSrcB2
• [x] generates thumbnail
• [x] ipfs add localPathVideoSrcB2 => videoSrcHash
• [x] save videoSrcHash in db
• [x] create 240p encode, add to db
• [x] pin add videoSrcHash on the cluster
• [x] pin add video240Hash on the cluster
• [x] trigger website build

This issue supersedes #126

[insanity54]

implemented in https://github.com/insanity54/futureporn-qa/tree/f8cc6d4