Proposal: Describe possible project structure and implications

Initial thoughts around scoping Kubernetes resources to projects and the associated implications.

Intended as a complement to #891, but with more detail on the implementation consequences of project scoping throughout the stack.

Would like to get general agreement on an outline to proceed against to support an initial prototype in next couple weeks.
Should a label key that is applied by the kubernetes system itself have a name like `kubernetes.io/project`  rather than just plain `project`, to avoid collision with user defined keys?  Thoughts @bgrant0607