chore: update core deps

[grabbou]

Per Uniswap/interface#6974 (comment), we're relaxing dependency on the core to use semver. This will make it easier to update the codebase as a whole and avoid duplicate entries in the interface.

Since @uniswap/swap-router-contracts is the one that consumes core directly, dependency on it its being relaxed too.

[zzmp]

lgtm - please make sure to run npx yarn-deduplicate && yarn install again to weed out any duplicates that are left.

[grabbou]

@zzmp do we run yarn-deduplicate as a standard part of release pipeline for libraries? AFAIK for libraries this is not that relevant, we're no shipping them along the package and usually prefer testing against latest environment.

[zzmp]

if the point of this is to avoid duplicate entries, you should still update the lockfile to do so. it also makes it more obvious if something is defined incorrectly.

[grabbou]

if the point of this is to avoid duplicate entries, you should still update the lockfile to do so

You are right, but the problem happens in the parent package that consumes all different Uniswap packages, not here in development (we will run dedupe in interface when all packages are upgraded). Running that is a good practice, but is separate from this PR. I've run it anyway, will default to running in the future then too.