Update repo captains

[UlisesGascon]

I just added myself to the packages that I plan to put a lot of energy going on 🥳

cc: @expressjs/express-tc

[sheplu]

LGTM in itself but wasn't the purpose of the repo captain to only have one per repository? for some package it seems that half the TC is a captain, hence we don't really have one captain :D

what do you think @expressjs/express-tc

[wesleytodd]

LGTM!

[wesleytodd]

wasn't the purpose of the repo captain to only have one per repository?

I didn't intend that when I proposed it, in fact I intended the opposite. Re reading this section though I wonder if we need to clarify:

Any TC member or existing captain on the repo can nominate another committer to the captain role, submit a PR to this doc, in the Active Project Captains section (maintaining the sort order) with the project, their GitHub handle and npm username (if different).

My original intent when @gireeshpunathil and I worked on this was that we would have a few captains on each repo (for redundancy and sustainability). I could see two changes to this wording that would help clarify:

1. "Repos can have as many captians as makes sense for the scope of work"
2. "an TC member or repos captian on the same project can nominate" (to clarify that a repo captian from another project should not nominate a captian for a differnt project.

[bjohansebas]

It would be good to include the changes proposed by @wesleytodd