docs: update code scanning tools label

[breezeFur]

Why:

Closes #45397

What's being changed:

The code scanning tools banner now uses Tools instead of Tool status. This PR updates the instruction text, the image alternative text, and the screenshot so the procedure matches the current interface.

Validation:

• npm run lint-content -- --paths content/code-security/how-tos/find-and-fix-code-vulnerabilities/manage-your-configuration/use-the-tools-status-page-for-code-scanning.md passed.
• git diff --check passed.
• The requested changed-content Vitest could not start in this Windows checkout because the repository's alias configuration resolves @/frame/start-server through the original non-ASCII workspace path. No test assertion ran.

Check off the following:

• A subject matter expert has reviewed the technical accuracy of the content.
• The changed content is limited to the terminology reported in the linked issue and its matching screenshot.
• All CI checks are passing.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
code-security/how-tos/find-and-fix-code-vulnerabilities/manage-your-configuration/use-the-tools-status-page-for-code-scanning.md	fpt ghec ghes@ 3.21 3.20 3.19 3.18 3.17	fpt ghec ghes@ 3.21 3.20 3.19 3.18 3.17

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.