fix: use "unjs/pathe" to make the exported type use relative path

[Chrissi2812]

Types of changes

• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

The generated types file .nuxt/types/supabase-database.d.ts contains broken paths examples I tested

path	nuxt.config.ts	supabase-database.d.ts
/app/types/database.types.ts	~/types/database.types.ts	../..app/types/database.types.ts
/types/database.types.ts	~~/types/database.types.ts	../..types/database.types.ts

The problem is the missing / before the directory name.

So I instead of using a string replacement, it now uses unjs/pathe relative to resolve the path correctly

Resolves: #515

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes (if not applicable, please state why)

How can I add tests for this kind of change? I tested these changes manually in my Nuxt 4 Project.

Manual testing:

1. Run npm run dev:prepare
2. Take a look at playgrounds .nuxt/types/supabase-database.d.ts file. Wrong path is used.

export * from '../..types/database.types.ts'

3. Use this PR and do the same. Now the path should be correct like this

export * from '../../types/database.types.ts'

[netlify]

👷 Deploy request for n3-supabase pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	c469b4f

[vercel]

@Chrissi2812 is attempting to deploy a commit to the NuxtLabs Team on Vercel.

A member of the Team first needs to authorize it.

[pkg-pr-new]

npm i https://pkg.pr.new/@nuxtjs/supabase@516

commit: c469b4f

[BritLuey]

Tested changes manually in my Nuxt 4 project; no issues.
Low risk change. Would solve main pain point of using this module with Nuxt 4 and Typescript