fix(ConfigProvider.fromEnv): use import.meta.env instead of process.env

The reason for this is that this allows using environment variables in the browser with vite. Vite has a feature where all environment variables that have a VITE_ prefix are exposed in import.meta.env. And even in node.js import.meta.env is a alias to process.env so i don't see any reason why ConfigProvider.fromEnv only supported process.env

Author: coffeeispower

packages/effect/src/internal/configProvider.ts

@@ -108,8 +108,7 @@ export const fromEnv = (
   const makePathString = (path: ReadonlyArray<string>): string => pipe(path, Arr.join(pathDelim))
   const unmakePathString = (pathString: string): ReadonlyArray<string> => pathString.split(pathDelim)
 
-  const getEnv = () =>
-    typeof process !== "undefined" && "env" in process && typeof process.env === "object" ? process.env : {}
+  const getEnv = () => import.meta.env;
 
   const load = <A>(
     path: ReadonlyArray<string>,