docs: add recommendation to use closures for configurable extensions

[WojtekTheWebDev]

trafficstars

🔗 Linked issue

IN-3969

❓ Type of change

• [x] 📖 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

Closures should be a recommended approach when it comes to creating a configurable extensions.

📝 Checklist

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

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 756440769fc8ebe59f6d4e128edc73ff69ceecf7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR