This adds some very simple, hardcoded endpoints for the /projects and /workspaces - just enough test data to exercise the flow in the UI:

		// Projects endpoint
		r.Route("/projects", func(r chi.Router) {
			r.Route("/{organization}", func(r chi.Router) {
				// TODO: Authentication
				// TODO: User extraction
				// TODO: Extract organization and add to context
				r.Get("/", api.projectService.getProjects)
				r.Post("/", api.projectService.createProject)

				r.Get("/{projectId}", api.projectService.getProjectById)
				// TODO: Get project by id
			})
		})

		// Workspaces endpoint
		r.Route("/workspaces", func(r chi.Router) {
			r.Route("/{organization}", func(r chi.Router) {
				r.Get("/", api.workspaceService.getWorkspaces)
				r.Get("/{workspaceId}", api.workspaceService.getWorkspaceById)
			})
		})		

With this, I can use the develop.sh script and get a server that sends data back for those APIs:

In order to facilitate this, I brought in the xjson library... which then required several other additional libraries:

• srverr
• validate
• longid
• buildmode

...and some external libraries:

• github.com/asaskevich/govalidator
• github.com/go-playground/validator/v10
• k8s.io/utils

There's a couple possible next steps:

• This might be completely superceded by work @kylecarbs is doing - so it's fine if this goes away and replaced by a more robust set of APIs! We can still discuss the types and make sure we have parity on the API surface.
• We could merge this as scaffolding to build out the API routes - there's a lot left to be plumbed and connected to the actual provisioners.

Related to #23