fix(nuxt): check has pinia module

[dnldsht]

Description

This PR fixes an issue that occurs when a Nuxt module adds another module internally.

For example, if you add the following in a Nuxt module:

installModule('@pinia/nuxt')
installModule('pinia-plugin-persistedstate/nuxt')

It triggers the following error:

The `@pinia/nuxt` module was not found, `pinia-plugin-persistedstate/nuxt` will not work.

This issue arises due to the way the `hasNuxtModule function operates:

function hasNuxtModule(moduleName, nuxt = useNuxt()) {
  return nuxt.options._installedModules.some(({ meta }) => meta.name === moduleName) || // check modules to be installed
  nuxt.options.modules.some((m) => moduleName === resolveNuxtModuleEntryName(m))
}

The meta name of @pinia/nuxt is always pinia in _installedModules. @pinia/nuxt is only present in nuxt.options.modules when declared in the nuxt.config

The root of the problem lies in the meta.name property. For @pinia/nuxt, its meta.name is always pinia in nuxt.options._installedModules. However, @pinia/nuxt is only present in nuxt.options.modules when explicitly declared in nuxt.config.

To reproduce the issue, check this Stackblitz example:

https://stackblitz.com/edit/github-ymapkt?file=src%2Fmodule.ts

re-review

[prazdevs]

alright checked for most cases, and it seems to work better this way ! 👍