Create high-level motivation document

[tomncooper]

We need to create an introduction document that lays out why GitOps is preferable to ClickOps for production infrastructure.

This document should describe what ClickOps is, the problems that can arise from it and give motivating examples of how a GitOps based approach would be better.

For example, short stories involving characters being tasked with deploying "a Kafka cluster just like this one", or a "user with the same access as this one" under ClickOps and what a mess that can be, compared to doing it through GitOps. Similarly, a description of a production incident where a character has to spend time figuring out what a colleague changed yesterday via ClickOps so it can be rolled back, is a good motivator for a GitOps system.

The document should also describe the common technologies and approaches for implementing GitOps.