Update ipfs.yml

[cewood]

Per conversation with Mosh at the IPFS Foundation, reverting some permissions from the last PR.

cc/ @mishmosh

[github-actions]

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

Access Changes

User 2color:
  - will lose push permission to 2019.ipfs.camp
  - will lose push permission to aegir
  - will lose push permission to benchmarks
  - will lose push permission to boxo
  - will lose push permission to distributions
  - will lose push permission to eslint-config-ipfs
  - will lose push permission to fs-repo-migrations
  - will lose push permission to go-bitfield
  - will lose push permission to go-block-format
  - will lose push permission to go-bs-sqlite3
  - will lose push permission to go-cid
  - will lose push permission to go-cidutil
  - will lose push permission to go-datastore
  - will lose push permission to go-detect-race
  - will lose push permission to go-dnslink
  - will lose push permission to go-ds-badger
  - will lose push permission to go-ds-crdt
  - will lose push permission to go-ds-flatfs
  - will lose push permission to go-ds-leveldb
  - will lose push permission to go-ds-measure
  - will lose push permission to go-ds-redis
  - will lose push permission to go-ds-s3
  - will lose push permission to go-ds-sql
  - will lose push permission to go-ds-swift
  - will lose push permission to go-fs-lock
  - will lose push permission to go-graphsync
  - will lose push permission to go-ipfs-archived
  - will lose push permission to go-ipfs-blocksutil
  - will lose push permission to go-ipfs-cmds
  - will lose push permission to go-ipfs-delay
  - will lose push permission to go-ipfs-example-plugin
  - will lose push permission to go-ipfs-pq
  - will lose push permission to go-ipld-cbor
  - will lose push permission to go-ipld-eth-import
  - will lose push permission to go-ipld-format
  - will lose push permission to go-ipld-git
  - will lose push permission to go-ipld-legacy
  - will lose push permission to go-ipld-zcash
  - will lose push permission to go-libipfs-rapide
  - will lose push permission to go-log
  - will lose push permission to go-merkledag
  - will lose push permission to go-metrics-interface
  - will lose push permission to go-metrics-prometheus
  - will lose push permission to go-peertaskqueue
  - will lose pull permission to go-qringbuf
  - will lose push permission to go-todocounter
  - will lose push permission to go-unixfsnode
  - will lose push permission to hang-fds
  - will lose push permission to helia
  - will lose push permission to helia-cli
  - will lose push permission to helia-delegated-routing-v1-http-api
  - will lose push permission to helia-verified-fetch
  - will have the permission to in-web-browsers change from push to pull
  - will lose pull permission to ipfs-companion
  - will lose push permission to ipfs-desktop
  - will lose push permission to ipfs-ds-postgres
  - will lose admin permission to ipfs-gui
  - will lose push permission to ipfs-update
  - will lose push permission to ipfs-webui
  - will lose push permission to ipget
  - will lose push permission to ipld-explorer-components
  - will lose push permission to iptb
  - will lose push permission to iptb-plugins
  - will lose push permission to js-dag-service
  - will lose push permission to js-datastore-pubsub
  - will lose push permission to js-fs-pull-blob-store
  - will lose pull permission to js-hamt-sharding
  - will lose push permission to js-idb-pull-blob-store
  - will lose push permission to js-ipfs-bitswap
  - will lose push permission to js-ipfs-merkle-dag
  - will lose push permission to js-ipfs-repo
  - will lose push permission to js-ipfs-unixfs
  - will lose push permission to js-ipfs-utils
  - will lose push permission to js-ipfsd-ctl
  - will lose push permission to js-ipns
  - will have the permission to js-kubo-rpc-client change from push to pull
  - will lose push permission to js-level-pull-blob-store
  - will have the permission to kubo change from push to pull
  - will lose push permission to protons
  - will lose push permission to public-gateway-checker
  - will have the permission to specs change from push to triage

[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:
  - destroy

Terraform will perform the following actions:

  # github_team_membership.this["repos - go:2color"] will be destroyed
  # (because key ["repos - go:2color"] is not in for_each map)
  - resource "github_team_membership" "this" {
      - etag     = "W/\"d5acb38354d81ca71d3770a54b1e915adccd8051ceabbf5e45e9971f8751fb41\"" -> null
      - id       = "3232508:2color" -> null
      - role     = "member" -> null
      - team_id  = "3232508" -> null
      - username = "2color" -> null
    }

  # github_team_membership.this["repos - javascript:2color"] will be destroyed
  # (because key ["repos - javascript:2color"] is not in for_each map)
  - resource "github_team_membership" "this" {
      - etag     = "W/\"adc723fc87ad16b6752cfced6988e8488953554e22c9fafcaccee4af1cc5f312\"" -> null
      - id       = "1433120:2color" -> null
      - role     = "member" -> null
      - team_id  = "1433120" -> null
      - username = "2color" -> null
    }

  # github_team_membership.this["wg gui/ux:2color"] will be destroyed
  # (because key ["wg gui/ux:2color"] is not in for_each map)
  - resource "github_team_membership" "this" {
      - etag     = "W/\"2d706c697d477568e858102e92c4ce224884d35896d18e3b3fbb6b5aa2243f3f\"" -> null
      - id       = "2825335:2color" -> null
      - role     = "member" -> null
      - team_id  = "2825335" -> null
      - username = "2color" -> null
    }

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