[chore] Reflect current TC sponsors on workstreams.yml

[mx-psi]

Follows #3366, this is another subset of #3337 that reflects the state of TC sponsorship on this private spreadsheet https://docs.google.com/spreadsheets/d/1xSofsYJUSp2YxiNBxnT8ZCCEwW_5_QwldWozmyEpjns/edit?gid=0#gid=0

[jsuereth]

@carlosalberto would you say this is guiding? E.g. the attribute-context work seems a bit more intense than just escalating, or is that unrelated to this SIG?

[jsuereth]

This generally LGTM -

Made some comments on changes I believe we made but didn't update the sheet. One for @carlosalberto to confirm.

[jack-berg]

Point of process: The referenced google sheet is out of date. Should this PR:

1. Reflect the information in the google sheet and save correcting for a future PR
2. Or should we do a round of updating / correction

I lean towards 2 because I don't think that updating will be contentious. The level of sponsorship reflects the current TC member's engagement in the SIG (not the community's desired engagement), and its subjective based on their interpretation of what they're doing.

With those rules in mind, I think we should be able to agree on updates quickly.

[mx-psi]

From my side, I am happy to update it to whatever the Technical Committee agrees on

[jsuereth]

Point of process: The referenced google sheet is out of date. Should this PR:

1. Reflect the information in the google sheet and save correcting for a future PR
2. Or should we do a round of updating / correction

I lean towards 2 because I don't think that updating will be contentious. The level of sponsorship reflects the current TC member's engagement in the SIG (not the community's desired engagement), and its subjective based on their interpretation of what they're doing.

With those rules in mind, I think we should be able to agree on updates quickly.

I vote for 2