Migrate site to fluvio repo

[tjtelan]

(This is maybe more of a discussion?)

Github Actions features have progressed enough that it might be convenient to migrate this website into the main repo to reduce the context switch for devs, and take advantage of processes and automation in that repo.

We're obviously tightly coupled to the functionality of fluvio and committed to a monorepo. So personally I feel it is acceptable to formalize this relationship further and move the repo the website code lives in. The intent being updates to Fluvio can more quickly be reflected on the website because we'll be able to identify requirements to update during CI, and we can also address #460 as part of our release processes. We'll also have an opportunity to re-evaluate Hugo (or at least start over to clean up unneeded code)

Processes would need to change, but we can scope CI to run updates based on the path changed, and update using direct upload during release.