chore: add hsanjuan to shipyard team

[lidel]

Summary

@hsanjuan joined @ipfs/shipyard

Why do you need this?

What else do we need to know?

DRI: myself

Reviewer's Checklist

• It is clear where the request is coming from (if unsure, ask)
• All the automated checks passed
• The YAML changes reflect the summary of the request
• The Terraform plan posted as a comment reflects the summary of the request

[github-actions]

The following access changes will be introduced as a result of applying the plan:

Access Changes

User hsanjuan:
  - will have the permission to boxo change from push to maintain
  - will have the permission to kubo change from push to maintain
  - will gain maintain permission to helia
  - will gain maintain permission to helia-cli
  - will gain maintain permission to helia-delegated-routing-v1-http-api
  - will gain maintain permission to helia-http-gateway
  - will gain maintain permission to helia-remote-pinning
  - will gain maintain permission to helia-verified-fetch
  - will gain maintain permission to rainbow
  - will gain admin permission to service-worker-gateway
  - will gain maintain permission to someguy

[github-actions]

Before merge, verify that all the following plans are correct. They will be applied as-is after the merge.

Terraform plans

ipfs

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # github_team_membership.this["shipyard:hsanjuan"] will be created
  + resource "github_team_membership" "this" {
      + etag     = (known after apply)
      + id       = (known after apply)
      + role     = "member"
      + team_id  = "11478581"
      + username = "hsanjuan"
    }

Plan: 1 to add, 0 to change, 0 to destroy.