Fix ESM compatibility in Metro project path resolution

[rklomp]

Please read and mark the following check list before creating a pull request:

• I read and followed the CONTRIBUTING.md guide.
• I read and followed the New Feature Checklist guide.

Short description of what this resolves:

Fixes an __dirname is not defined runtime error in the ESM build of @ui-kitten/metro-config.

@ui-kitten/metro-config is distributed with an ESM build, but project.service.js uses the CommonJS-specific __dirname global:

const PROJECT_PATH = Path.resolve(__dirname, '../../../../');

When the ESM build is loaded by modern Node.js versions, __dirname is not defined and Metro configuration fails to initialize:

ReferenceError: __dirname is not defined in ES module scope

Derive __dirname from import.meta.url using Node's standard ESM-compatible APIs:

const __filename = fileURLToPath(import.meta.url);
const __dirname = Path.dirname(__filename);

This preserves the existing path resolution while making the ESM build compatible with Node.js ESM semantics and Windows path handling.

Tested with:
Expo 57
React Native 0.86
Node.js 22
Windows

The Metro configuration successfully initializes after applying this change