fix(code-security): update advanced CodeQL setup links

[aniruddhaadak80]

Why:

Closes #46077

Four CodeQL articles still used the legacy advanced-setup route in their permissions frontmatter. That route resolves through a redirect, while the current article is available at the stable path used by the rest of the CodeQL documentation. Updating the source removes the redirect hop without changing the permissions text or product behavior.

What's being changed (if available, include any code snippets, screenshots, or gifs):

• Update the advanced CodeQL setup link in four CodeQL articles to /code-security/how-tos/find-and-fix-code-vulnerabilities/configure-code-scanning/configuring-advanced-setup-for-code-scanning.
• Keep all surrounding frontmatter, versioning, and article content unchanged.
• This is a content-only link correction with no generated, translated, workflow, or site-code changes.

Validation completed with Node.js v24.19.0:

• npm run build — passed.
• npm run lint-content -- --paths content/code-security/concepts/code-scanning/codeql/codeql-for-compiled-languages.md content/code-security/how-tos/find-and-fix-code-vulnerabilities/manage-your-configuration/codeql-for-compiled-languages.md content/code-security/reference/code-scanning/codeql/build-options-for-compiled-languages.md content/code-security/reference/code-scanning/workflow-configuration-options.md — passed with no errors.
• npm test -- --no-file-parallelism --maxWorkers=1 src/content-render/tests/render-changed-and-deleted-files.ts with all four edited files in CHANGED_FILES — 2 tests passed.
• npm run check-links-pr -- --files content/code-security/concepts/code-scanning/codeql/codeql-for-compiled-languages.md content/code-security/how-tos/find-and-fix-code-vulnerabilities/manage-your-configuration/codeql-for-compiled-languages.md content/code-security/reference/code-scanning/codeql/build-options-for-compiled-languages.md content/code-security/reference/code-scanning/workflow-configuration-options.md — 57 links checked; all links valid.
• npm run tsc — passed.
• git diff --check — passed.

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 review environment.

[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/concepts/code-scanning/codeql/codeql-for-compiled-languages.md	fpt ghec ghes@ 3.22 3.21 3.20 3.19 3.18 3.17	fpt ghec ghes@ 3.22 3.21 3.20 3.19 3.18 3.17
code-security/how-tos/find-and-fix-code-vulnerabilities/manage-your-configuration/codeql-for-compiled-languages.md	fpt ghec ghes@ 3.22 3.21 3.20 3.19 3.18 3.17	fpt ghec ghes@ 3.22 3.21 3.20 3.19 3.18 3.17
code-security/reference/code-scanning/codeql/build-options-for-compiled-languages.md	fpt ghec ghes@ 3.22 3.21 3.20 3.19 3.18 3.17	fpt ghec ghes@ 3.22 3.21 3.20 3.19 3.18 3.17
code-security/reference/code-scanning/workflow-configuration-options.md	fpt ghec ghes@ 3.22 3.21 3.20 3.19 3.18 3.17	fpt ghec ghes@ 3.22 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.

[subatoi]

Thanks @aniruddhaadak80—we do have redirects in place so there's no need to raise a large number of PRs to fix any old links, but we appreciate your contribution and I'll go ahead and merge this

[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 ⚡