docs: list current Committers + bjohansebas nomination

[UlisesGascon]

This PR list current Committers for projects.

• Ref: Add carpasse as repo captain for response-time #5768 (cc: @carpasse )
• Currently @bjohansebas requested committer access in compression (Update captains #6027 (comment)).

Note: I am +1 in the nomination, he have done non-trivial contributions in the project for a while. Note that I am repo captain for compression too (#6027)

cc: @expressjs/express-tc

[bjohansebas]

Hi @UlisesGascon, I can also be part of the committee for the website. I've been helping with the site by updating its documentation and improving its design for several months now. What do you think?

cc: @crandmck

[blakeembrey]

What's the difference between this and ### Active Projects and Captains? Can we merge them? Ideally there isn't two different project lists and committers, it seems like the captains should be updated instead?

[UlisesGascon]

Based on the last discussion (context) comitters and captains are different roles (different access level and responsibilities). Also currently we manage that in different Github teams.

Maybe we can use the same project list and add a sub-list in each project for the captains and comitters. So we duplicate less. But not sure if that solves the thing 🤔

[blakeembrey]

Got it, I think it makes sense for them to be separate. Should this be a list we commit or can we manage it in GitHub and make the teams public?

If you really want to commit it, maybe move it below the current active project list and make it a sub-title like Active Committers? Having two sections in a long document calls "active projects" is my main confusion, and committing committers or putting them first makes less sense as I assume this document is the one which we expect people to attend to when they need to contact the DRI for a project.

[blakeembrey]

I see more collaborators in the list here that aren't being committed: https:/orgs/expressjs/teams.