Update file and directory names to use backticks

[paulinek13]

Why:

Closes: (No issue created)

This change ensures that file and directory names in the content/actions/use-cases-and-examples/building-and-testing/ directory comply with the style guide. Proper formatting improves readability and consistency throughout the documentation.

What's being changed:

Updated file and directory names in the following files to use backticks as required by the style guide:

• content/actions/use-cases-and-examples/building-and-testing/building-and-testing-java-with-ant.md
• content/actions/use-cases-and-examples/building-and-testing/building-and-testing-java-with-gradle.md
• content/actions/use-cases-and-examples/building-and-testing/building-and-testing-java-with-maven.md
• content/actions/use-cases-and-examples/building-and-testing/building-and-testing-nodejs.md
• content/actions/use-cases-and-examples/building-and-testing/building-and-testing-python.md
• content/actions/use-cases-and-examples/building-and-testing/building-and-testing-ruby.md
• data/reusables/actions/setup-node-intro.md

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the preview environment.

[github-actions]

👓 Previews for changed content

This comment is 🤖 automatically generated and will be overwritten every time changes are committed to this branch.

The table contains an overview of files in the content directory that have been changed in this pull request. It's provided to make it easy to review your changes on the review server. Please note that changes to the data directory will not show up in this table.

---

Content directory changes

You may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.

Source	Preview	Production	What Changed
actions/use-cases-and-examples/building-and-testing/building-and-testing-java-with-ant.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10
actions/use-cases-and-examples/building-and-testing/building-and-testing-java-with-gradle.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10
actions/use-cases-and-examples/building-and-testing/building-and-testing-java-with-maven.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10
actions/use-cases-and-examples/building-and-testing/building-and-testing-nodejs.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10
actions/use-cases-and-examples/building-and-testing/building-and-testing-python.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10
actions/use-cases-and-examples/building-and-testing/building-and-testing-ruby.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10
actions/use-cases-and-examples/publishing-packages/publishing-nodejs-packages.md	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	fpt ghec ghes@ 3.15 3.14 3.13 3.12 3.11 3.10	from reusable

---

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server
This table is posted from the Content Changes Table Comment workflow.

[subatoi]

Hi @paulinek13 many thanks! Please feel free to open more of these in other parts of our docs, if you wish

I'll go ahead and add this to the merge queue—you'll see some automation notifying you when this is merged, and it will go live on the docs site after that

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡