fix(markdown): detect inline component followed non whitespace characters

[farnabaz]

🔗 Linked issue

resolves #1217

❓ 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

📝 Checklist

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

[netlify]

✅ Deploy Preview for nuxt-content ready!

Name	Link
🔨 Latest commit	750311e
🔍 Latest deploy log	https://app.netlify.com/sites/nuxt-content/deploys/62a1b1d8cfb8eb000853874b
😎 Deploy Preview	https://deploy-preview-1227--nuxt-content.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 settings.

[leipert]

@farnabaz thanks for getting started right away. I think there should be more characters allowed than just dot and comma. Question marks, exclamation marks, colons, semi colons, etc.

I wonder (especially if you used square brackets and curly brackets before), if just any character that cannot be used in a component name should be allowed.

[farnabaz]

@leipert You are right, only ASCII chars, -, _ and : can create invalid results when they appear at the end of an inline component. Other characters are safe to use.
Also for using -, _ and : at the end of a component we can create a dummy attribute for the component. :hello{}-world