Stop using the --exact flag when publishing packages with Lerna.

This follows-up on f710fe4, to see what
happens when we allow wider ranges of versions in depended-upon packages by
utilizing the caret semantic-versioning operator (i.e. `^`).

While I wasn't convinced this was fail-safe, I still think that the changes
in f710fe4 add some value when _also_
applying this change.

In particular, in my current workflow, I'm publishing a new version of
Apollo Server using the `release:server` npm script, and it wants to also
publish new versions of `@apollo/gateway` and `@apollo/federation` merely
because they are depending on `apollo-server-core` and currently specify
their dependency without the caret semver operator.

Note: We'll need to wait until the publish after this to see what the
effects are (since the first publish will introduce the caret operator), but
let's see how this goes! 🧪

cc @trevor-scheer

Author: abernix

package.json

@@ -8,7 +8,7 @@
     "compile": "tsc --build tsconfig.build.json",
     "compile:clean": "tsc --build tsconfig.build.json --clean",
     "watch": "tsc --build tsconfig.build.json --watch",
-    "release": "npm run clean && npm ci && lerna publish --exact --include-merged-tags",
+    "release": "npm run clean && npm ci && lerna publish --include-merged-tags",
     "release:server": "npm run release -- --force-publish=apollo-server,apollo-server-core,apollo-server-azure-functions,apollo-server-cloud-functions,apollo-server-cloudflare,apollo-server-express,apollo-server-fastify,apollo-server-hapi,apollo-server-koa,apollo-server-lambda,apollo-server-micro,apollo-server-testing,apollo-server-integration-testsuite,apollo-server-env,apollo-tracing,apollo-server-types,graphql-extensions,apollo-cache-control,apollo-datasource,apollo-engine-reporting,apollo-server-errors,apollo-server-plugin-base",
     "release:federation": "npm run release -- --force-publish=@apollo/federation,@apollo/gateway",
     "postinstall": "lerna run prepare && npm run compile",