Fix compilation failure with using Ably on Next.js with turbopack

Using `serverComponentsExternalPackages` nextjs config option to fix
"Module not found" errors during compilation when running nextjs with
turbopack (`next dev --turbo`). See explanation for the issue and the
solution at ably/ably-js#1699 (comment).

Also removes the need to use `overrides` in package.json and `webpack`
field in next.config.js introduced in 3d51768
to fix `Critical dependency: the request of a dependency is an expression`
warnings

Author: VeskeR

next.config.js

@@ -9,13 +9,9 @@ const nextConfig = {
     dangerouslyAllowSVG: true,
     domains: ['static.ably.dev'],
   },
-  webpack: (config) => {
-    config.externals.push({
-      'utf-8-validate': 'commonjs utf-8-validate',
-      'bufferutil': 'commonjs bufferutil',
-    })
-    return config
-  },  
-}
+  experimental: {
+    serverComponentsExternalPackages: ['ably'],
+  },
+};
 
-module.exports = nextConfig
+module.exports = nextConfig;

package-lock.json

@@ -13,7 +13,7 @@
     "@types/node": "20.6.5",
     "@types/react": "18.2.22",
     "@types/react-dom": "18.2.7",
-    "ably": "1.2.44",
+    "ably": "^1.2.44",
     "dotenv": "^16.0.3",
     "eslint": "8.50.0",
     "flowbite": "^1.8.1",
@@ -31,10 +31,5 @@
     "eslint-plugin-react-hooks": "^4.6.0",
     "postcss": "^8.4.28",
     "tailwindcss": "^3.3.3"
-  },
-  "overrides": {
-    "cacheable-request": {
-      "keyv": "npm:@keyvhq/core@~1.6.6"
-    }
   }
-}
+}