fix: actually resolve the ref in resolvePath

[mattmess1221]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSDoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

ACTUALLY resolve the path parameter refs.

Turns out I missed the whole point in #39. I guess that's what I get for rushing a push on a Friday afternoon.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[netlify]

✅ Deploy Preview for nuxt-api-party ready!

Name	Link
🔨 Latest commit	723a4f9
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt-api-party/deploys/64ecbacca2c9cf0008ede74a
😎 Deploy Preview	https://deploy-preview-40--nuxt-api-party.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[johannschopplich]

Shouldn't be necessary with the getter syntax:

pathParams: () => ({
  id: id.value
})

But I trust you this change is necessary in your use-case. Accepted.