add back hanabi1224 and AlexeyKrasnoperov to org and forest

[LesnyRumcajs]

Summary

Not sure why they were removed in cb18005 after I added them in #142. Adding them back; they're active Forest team members.

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 alexeykrasnoperov:
  - will join the organization as a [object Object] (remind them to accept the email invitation)
  - will gain push permission to builtin-actors
  - will gain push permission to f3-activation-contract
  - will gain push permission to fips
  - will gain push permission to fvm-test-vectors
  - will gain maintain permission to ref-fvm
User hanabi1224:
  - will join the organization as a [object Object] (remind them to accept the email invitation)
  - will gain push permission to builtin-actors
  - will gain push permission to f3-activation-contract
  - will gain push permission to fips
  - will gain push permission to fvm-test-vectors
  - will gain maintain permission to ref-fvm

[github-actions]

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

Terraform plans

filecoin-project

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

  # github_membership.this["hanabi1224"] will be created
  + resource "github_membership" "this" {
      + etag     = (known after apply)
      + id       = (known after apply)
      + role     = "member"
      + username = "hanabi1224"
    }

  # github_team_membership.this["forest:alexeykrasnoperov"] will be created
  + resource "github_team_membership" "this" {
      + etag     = (known after apply)
      + id       = (known after apply)
      + role     = "member"
      + team_id  = "4043513"
      + username = "AlexeyKrasnoperov"
    }

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

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

[BigLep]

I don't know why they were removed in cb18005

That is a sync job that synchronizes this repo with what is actually the state of truth in github. This seems odd, but one potential explanation is they were removed in the github UI and the sync job just picked it up. (We'd have to check the GitHub audit log to understand if that happened and who did it. I'll go down that path if it happens again.)

Maybe @galargh has other ideas?