Create API Controller for Tees collection

[pkskelly]

Create API Controller to handle API requests for Tees. Include the following endpoints and a model for the Tee entity. Tees should be persisted as part of the Course object in Cosmos. Unit tests should be HTTP driven to test the API not against the internal class implementation.

• [x] Update API to accept a /courses/{id}/tees GET request - [ ] Update API to accept a /courses/{id}/tees POST request - [ ] Update API to accept a /courses/{id}/tees/{id} GET request - [ ] Update API to accept a /courses/{id}/tees/{id} DELETE request

[pkskelly]

Changed the approach to manage tees from the Course controller for now. Since storing a Course can contain Tees, and CosmosDB is a better store for a single Course, this approach makes sense for now.

[pkskelly]

PR #46 completed this. The editing of Tees is done through the Course API endpoints. The inclusion of the /courses/{guid}/tees endpoint will enable listing tees for posting rounds in the future.