fix: comments being treated as errors

[hacknug]

🔗 Linked issue

Fixing this was easier than opening an issue 😇

❓ 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)
• ✨ 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

This PR prevents the module from treating comments as errors and logging them to the console.

I looked into pushing the comments to currentGroup.comments.push(comment) to later restore them but, as mentioned in your comment (comments are too hard to parse in a logical order, we'll just omit them), it makes things unnecessarily complicated and would require rewriting other parts of the module. Plus I would count getting rid of them as minification so I'm guessing it's a good thing.

I believe we can get rid of currentGroup.comment and the for loop where we restore the comments since we're not saving them at any point. Might have a very minor positive impact on sites with a big robots.txt file.

[harlan-zw]

Great contribution, thanks!

Feel free to send any subsequent PRs related to the optimization.