fixing the permissions on website-new

[dhuseby]

Summary

Fixes the permissions on the website-new repo so that I can merge more changes.

Why do you need this?

There is an outstanding PR in the website-new repo that cannot be merged because the website-new repo doesn't have the correct permissions granted. This PR gives the website-new repo the same permissions as the website repo.

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 achingbrain:
  - will have the permission to website-new change from pull to admin
User aschmahmann:
  - will gain admin permission to website-new
User biglep:
  - will gain admin permission to website-new
User dhuseby:
  - will have the permission to website-new change from pull to admin
User galargh:
  - will gain admin permission to website-new
User guillaumemichel:
  - will gain admin permission to website-new
User jbenet:
  - will gain admin permission to website-new
User jorropo:
  - will gain admin permission to website-new
User kubuxu:
  - will gain admin permission to website-new
User laurentsenta:
  - will gain admin permission to website-new
User lidel:
  - will gain admin permission to website-new
User marcopolo:
  - will gain admin permission to website-new
User momack2:
  - will gain admin permission to website-new
User mxinden:
  - will gain admin permission to website-new
User p-shahi:
  - will have the permission to website-new change from pull to admin
User raulk:
  - will have the permission to website-new change from pull to admin
User stebalien:
  - will have the permission to website-new change from pull to admin

[github-actions]

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

Terraform plans

libp2p

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_repository_collaborator.this["website-new:momack2"] will be created
  + resource "github_repository_collaborator" "this" {
      + id                          = (known after apply)
      + invitation_id               = (known after apply)
      + permission                  = "admin"
      + permission_diff_suppression = false
      + repository                  = "website-new"
      + username                    = "momack2"
    }

  # github_team_repository.this["admin:website-new"] will be created
  + resource "github_team_repository" "this" {
      + etag       = (known after apply)
      + id         = (known after apply)
      + permission = "admin"
      + repository = "website-new"
      + team_id    = "2077192"
    }

  # github_team_repository.this["ci:website-new"] will be created
  + resource "github_team_repository" "this" {
      + etag       = (known after apply)
      + id         = (known after apply)
      + permission = "push"
      + repository = "website-new"
      + team_id    = "2562372"
    }

  # github_team_repository.this["w3dt-stewards:website-new"] will be created
  + resource "github_team_repository" "this" {
      + etag       = (known after apply)
      + id         = (known after apply)
      + permission = "admin"
      + repository = "website-new"
      + team_id    = "4657013"
    }

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