s/hyperspace/filhyperspace

[ianconsolata]

use the full name (filhyperspace) for the FilHyperspace repo, and add FF IT as a backup administrator

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 akaladarshi:
  - will gain maintain permission to bellperson
User alexeykrasnoperov:
  - will gain maintain permission to bellperson
User elmattic:
  - will leave the organization
  - will lose push permission to builtin-actors
  - will lose push permission to f3-activation-contract
  - will lose push permission to fips
  - will lose push permission to fvm-test-vectors
  - will lose maintain permission to ref-fvm
User filecoinfoundation-inf:
  - will lose maintain permission to hyperspace
  - will gain admin permission to filhyperspace
User hanabi1224:
  - will gain maintain permission to bellperson
User ianconsolata:
  - will lose admin permission to hyperspace
  - will gain admin permission to filhyperspace
User joemocode-business:
  - will lose maintain permission to hyperspace
  - will gain maintain permission to filhyperspace
User kalambet:
  - will gain maintain permission to bellperson
User lanzafame:
  - will lose maintain permission to hyperspace
  - will gain maintain permission to filhyperspace
User lesnyrumcajs:
  - will gain maintain permission to bellperson
User parkan:
  - will lose maintain permission to hyperspace
  - will gain maintain permission to filhyperspace
User parthshah1:
  - will lose maintain permission to hyperspace
  - will gain maintain permission to filhyperspace
User relotnek:
  - will lose maintain permission to hyperspace
  - will gain maintain permission to filhyperspace
User sudo-shashank:
  - will gain maintain permission to bellperson

[ianconsolata]

@galargh This is trying to delete the old repo in order to do the rename, but can't because it's tagged with prevent_destroy-- I already manually renamed this in Github settings. Could we just import that state rather than trying to delete the old repo? I am worried explicitly deleting the old repo might mess with the redirect to the new name

[galargh]

Yes, it definitely would. Repo renames are not a supported feature here. Thanks for renaming thorugh the UI. I"m going to run the sync now.