fix(config): avoid serialization warning when primitives have prototype changed

[SoaresMG]

🔗 Linked issue

No issue, do I need to open it?

❓ 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

Unfortunately there are a few libs that inject utils into prototypes, with the current implementation of checkSerializableRuntimeConfig if String or any other primitive has an util injected into the prototype a warning is thrown.

I don't see any direct consequence of just ignoring it during the check, if that prototype is indeed needed it will be there once JSON.parse is used.

An example of this is forEachEmbeddedItem where the ContentStack team added an util into String.prototype.

I don't think libs should be polluting prototypes needlessly when it could very well be an exported function, but nitro shouldn't also be concerned about it since there is no consequence at all (right?).

Reproduction

📝 Checklist

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

[pi0]

❤️