[dependency maintenance] @effect/match -> effect migration

[ari-becker]

Description

a) proximate trigger: unmet peer dependency in syncpack 12:

 ERR_PNPM_PEER_DEP_ISSUES  Unmet peer dependencies

.
└─┬ syncpack 12.0.0
  └─┬ @effect/match 0.40.0
    └── ✕ unmet peer effect@2.0.0-next.47: found 2.0.0-next.62

I see that 0.40.0 is indeed the latest version of @effect/match:

However, the package links to a repository which has been archived:

Apparently there was some kind of migration, Effect now recommends import { Effect } from "effect" and Effect.match:

https://www.effect.website/docs/error-management/matching

Suggested Solution

Follow upstream changes to solve the peer dependency issue?

Workaround

package.json:

{
  "pnpm": {
    "peerDependencyRules": {
      "allowedVersions": {
        "@effect/match@0.40.0>effect": "2.0.0-next.62"
      }
    }
  }
}

[JamieMason]

I've switched this repo over to using pnpm strict, hopefully this is resolved in 12.0.1