chore: update component owner for AWS to jj22ee

[jj22ee]

Short description of the changes

• Followup of chore: mark AWS vendor packages as unmaintained #2415 (comment)

Discussed within the X-Ray team at AWS, I will take over ownership+maintenance duties of the AWS components from @carolabadeer, whose bandwidth is currently being focused outside of OTel.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.86%. Comparing base (1165264) to head (af64430).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2506   +/-   ##
=======================================
  Coverage   90.86%   90.86%           
=======================================
  Files         161      161           
  Lines        7858     7858           
  Branches     1612     1612           
=======================================
  Hits         7140     7140           
  Misses        718      718           

[github-actions]

This package does not have an assigned component owner and is considered unmaintained. As such this package is in feature-freeze and this PR will be closed with 14 days unless a new owner or a sponsor (a member of @open-telemetry/javascript-approvers) for the feature is found. It is the responsibility of the author to find a sponsor for this feature.
Are you familiar with this package? Consider becoming a component owner.

[pichlermarc]

Awesome, welcome @jj22ee - happy to have you on board 🎉

[pichlermarc]

@jj22ee have you considered joining the OTel Organization? That would allow us to auto-assign pull requests to you for the relevant packages. I'd gladly sponsor you joining the Org. :)

[jj22ee]

@pichlermarc Hey, thanks for approving this code-owner update. I do want to join the OTel Organization, thanks for offering to sponsor me to join. Please let me know what I need to do on my end to join.

[pichlermarc]

@jj22ee great to hear that. 🙌 Usually two sponsors from the organization are needed (from two different companies) - so you'd need to find one more person to sponsor you. You can find all the requirements to become a member in the community repo.

Once you have found a second sponsor and opened the request as outlined in the doc I linked, you can ping me on the CNCF slack and I'll comment to say that I support your membership request. 🙂

[trentm]

Hi @jj22ee, I'm happy to be a second sponsor for you.

[jj22ee]

Thanks @trentm!

I will follow-up soon to create the membership request.