gemfile.5: Code format the default glob to escape Markdown

[ParadoxV5]

What was the end-user or developer problem that led to this PR?

The default glob as rendered ({,,/*}.gemspec) doesn’t make sense.

What is your fix for the problem, implemented in this PR?

Quote the default glob in an inline code rather than double-quotes so the *s don’t and will never leak out as Markdown for emphasis.

Make sure the following tasks are checked

• Describe the problem/feature
• Write tests for features and bug fixes
• Write code to solve the problem
• Make sure you follow the current code style and write meaningful commit messages without tags

[welcome]

Thanks for opening a pull request and helping make RubyGems and Bundler better! Someone from the RubyGems team will take a look at your pull request shortly and leave any feedback. Please make sure that your pull request has tests for any changes or added functionality.

We use GitHub Actions to test and make sure your change works functionally and uses acceptable conventions, you can review the current progress of GitHub Actions in the PR status window below.

If you have any questions or concerns that you wish to ask, feel free to leave a comment in this PR or join our #rubygems or #bundler channel on Slack.

For more information about contributing to the RubyGems project feel free to review our CONTRIBUTING guide

[deivid-rodriguez]

Thanks!

[deivid-rodriguez]

@ParadoxV5 Would you be able to run rake man:build from the branch with your changes and commit the result? Our gemfile.5 file also needs this update, and that's what rake man:build does.

[ParadoxV5]

@ParadoxV5 Would you be able to run rake man:build from the branch with your changes and commit the result?

Not quite… I just patched the file on the GitHub web editor 😁. I’ll clone my fork locally rq.

[deivid-rodriguez]

Looks good @ParadoxV5, thank you!