fix: i18n layer vue i18n resolution

[BobbieGoede]

🔗 Linked issue

#2343

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 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)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This changes resolveLayerVueI18nConfigInfo to only try to resolve Vue I18n configuration paths for layers that contain configuration for @nuxtjs/i18n.

@kazupon would this be correct or is it possible and should we take into account layers could have an i18n.config file without using @nuxtjs/i18n?

📝 Checklist

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

[kazupon]

would this be correct or is it possible and should we take into account layers could have an i18n.config file without using @nuxtjs/i18n?

Yes, this is correct.
We shouldn't take into account an i18n.config file without using @nuxtjs/i18n.

[dargmuesli]

How is the vue-i18n config meant to be inferred from multiple layers? I would imagine configurations like fallbackWarn: false to bubble up, but it seems that a project has to set that configuration itself even if a layer it uses set it already.
I looked at the source code a bit and it seems to me that only messages are collected from the multiple vue-i18n configs? Is that right?