Rename codeql-analysis.yml to codeql.yml to fix stale code scanning configuration

The code scanning configuration still references .github/workflows/codeql.yml,
but the file was previously renamed to codeql-analysis.yml. Restoring the
original filename resolves the 'Actions workflow file not found' error.

Also updates CODE_SCANNING_SETUP.md to reflect the filename change and removes
the outdated section about the rename workaround.

Agent-Logs-Url: https://github.com/trimble-oss/modus-mobile-maui-components/sessions/5fe8a1aa-a4af-4b07-8504-a6f19ae83298

Co-authored-by: jeff-at-trimble <215895768+jeff-at-trimble@users.noreply.github.com>

Author: Copilot

.github/workflows/codeql-analysis.yml .github/workflows/codeql.yml.github/workflows/codeql-analysis.yml renamed to .github/workflows/codeql.yml

@@ -4,7 +4,7 @@ This document explains the CodeQL code scanning configuration for this repositor
 
 ## Current Configuration
 
-This repository uses a **custom CodeQL workflow** (`.github/workflows/codeql-analysis.yml`) that provides thorough analysis with the `security-and-quality` query suite.
+This repository uses a **custom CodeQL workflow** (`.github/workflows/codeql.yml`) that provides thorough analysis with the `security-and-quality` query suite.
 
 ### Workflow Details
 
@@ -13,12 +13,6 @@ This repository uses a **custom CodeQL workflow** (`.github/workflows/codeql-ana
 - **Build target**: `net9.0-android` (compatible with Ubuntu runners)
 - **Query suite**: `security-and-quality` (more thorough than default)
 
-## Previous Issue: Stale Configuration
-
-The original workflow file (`codeql.yml`) was **manually disabled** in GitHub Actions UI. A manually disabled workflow cannot be re-enabled through code changes alone — modifying the file content has no effect on the disabled state. This caused the code scanning status page to show a stale configuration error.
-
-The fix was to rename the workflow file from `codeql.yml` to `codeql-analysis.yml`. GitHub Actions identifies workflows by their file path, so the renamed file is treated as a new (active) workflow.
-
 ## Managing Duplicate Scanning Configurations
 
 If both the custom workflow and GitHub's **Default Setup** are active, you may see duplicate scan results. To avoid this: