[Dev env] Break down what functions are needed for development and deployment

[timmc-edx]

In our effort to decide how to move forward with improving, reworking, or replacing our development and deployment environments (devstack, tutor, etc.) we need to get a better sense of what those systems currently provide to us, and where they are lacking. This will help us answer questions like:

• Can the development environment work more like a production environment, maybe even by using the same software?
• Where should we look at tools to complement devstack, tutor, k8s, etc. vs improving them, wrapping them, or replacing them/creating alternatives?
• How much should information about how a service is developed or deployed live with the service repository vs. in a central place? Which would allow us more freedom of dev/deploy/orchestration options?
• Which of these features can realistically be supported agnostic of a docker-compose vs. Kubernetes choice, rather than needing to be duplicated for each option?
• What would leveraging one of the tools identified in [Discovery] Cloud-based developer environments #82 potentially gain us, and which aspects of the development environment would be largely unchanged (or need to be reworked without significant gain) by the choice?

Documents:

• Spreadsheet with breakdown and comparison: https://docs.google.com/spreadsheets/d/1XAipznjIcTaE2H454M74No2Ro_9VftbolfV4YVv-B9I/edit#gid=0
• Some cloud/local alternatives we might want to include in the comparison: https://openedx.atlassian.net/wiki/spaces/AC/pages/3647700997/Development+environment+notes

Acceptance criteria:

• Break out functions/features as rows of spreadsheet
• Add columns for current tools and options under investigation (and fill them out where applicable)