chore: adding web3-bot to the org and to the p2p-forge repository

[galargh]

Summary

chore: adding web3-bot to the org and to the p2p-forge repository

Why do you need this?

To add web3-bot's credentials to the p2p-forge repository.

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 web3-bot:
  - will join the organization as a [object Object] (remind them to accept the email invitation)
  - will gain push permission to p2p-forge

[github-actions]

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

Terraform plans

ipshipyard

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_membership.this["web3-bot"] will be created
  + resource "github_membership" "this" {
      + etag     = (known after apply)
      + id       = (known after apply)
      + role     = "member"
      + username = "web3-bot"
    }

  # github_repository_collaborator.this["p2p-forge:web3-bot"] will be created
  + resource "github_repository_collaborator" "this" {
      + id                          = (known after apply)
      + invitation_id               = (known after apply)
      + permission                  = "push"
      + permission_diff_suppression = false
      + repository                  = "p2p-forge"
      + username                    = "web3-bot"
    }

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