Add/ Edit / Bulk Upload Direct Reports

Right now, each meeting has a withWhom property that identifies whom the meeting was done with. The problem is that since this is by string, if two people have the same name, it would be impossible to distinguish between them. Employee as a separate entity just makes sense for this particular use case.

Also, this would allow people to create aggregations based on an employee, leading to employee-specific insights to come up.

No files or tests are named. Start by locating the meeting model or API handling the withWhom property, then trace how meeting aggregations are built; done should include a distinct employee entity that supports adding, editing, and bulk upload while allowing employee-specific insights.

Written by the indexing model from the issue text.