[JasMehta08]

What

Adds docs/team-roles.md: each member's area, issues by owner, report section owners and Satchel component owners.

Closes #16

Why

The Week 2 report (#18) needs a team roles section, and the course asks for an equal split. Everything follows the issues: assignees for ownership, and the deliverable issues (#10, #16, #18, #25, #28, #29, #37) for editors, the viva coordinator and the on-prem parts. That gives 11, 11 and 10 issues, plus two lead roles each.

How to check it

• Section 2 matches the assignees on the board and the editor or coordinator named in each deliverable issue.
• Section 3: section owners are the owners of the linked issues, as [Deliverable] Week 2: 10-page case study report #18 and [Deliverable] Week 3: report add-ons with results #37 say.
• Section 4: component owners are left "to be agreed in Create Week 3 build and experiment issues from the exercise plan #19" on purpose.
• Each member needs to approve this PR (issue [Docs] Create the Team Roles doc #16).

Please confirm in review

@frectrium @VyasGuru, a few report sections have no linked issue, so they're marked "to be agreed" in section 3. Let's settle them here:

• Week 2 report: References
• Week 3 add-ons: Changes from the exercise plan
• Final report: Conclusions, limitations and future work, and References

Checklist

• cargo fmt, cargo clippy and cargo test pass locally (code PRs)
• Tests added or updated for the change (code PRs)
• New sources are added to docs/sources/README.md (research PRs)
• Design decisions are recorded in the Design Decision Log
• Docs and README are updated if behaviour or setup changed

[frectrium]

@JasMehta08 two things here depend on issues and PRs that have changed since you opened this:

1. New calculator issues. The course also expects a programmatic cost calculator, so I've added [Cost] Cost calculator engine and CLI (satchel-cost) #52 (cost engine and CLI, you, Week 3), [Cost] Sizing model: blocks, volumes, drives, servers and cloud tiers for a workload #53 (sizing model, me, Week 3) and [Feature] Interactive pricing calculator web UI #54 (web UI, Guru, Week 4). Can you add them to sections 2 and 4? The counts become 11, 11 and 10.
2. Component owners. Section 4 waits on Create Week 3 build and experiment issues from the exercise plan #19, which waits on the exercise plan (docs(design): finalize the exercise plan with RS(6,3) on 9 nodes #56). That's fine to leave as "to be agreed in Create Week 3 build and experiment issues from the exercise plan #19" for now. I'll update the table when I create the issues, unless you'd rather do it.