[Sync] Update project files from source repository (4ee089a)

[mrz1836]

What Changed

• Removed the monolithic .github/.env.base configuration file (550 lines) containing all default configuration variables for GoFortress CI/CD workflows and tools
• Deleted .github/.yamlfmt configuration file
• Deleted .github/CODEOWNERS file
• Modified .github/actions/download-artifact-resilient/action.yml and .github/actions/load-env/action.yml
• Restructured environment configuration into multiple smaller files under .github/env/ directory: 00-core.env, 10-coverage.env, 10-security.env, 10-mage-x.env, 10-pre-commit.env, 20-redis.env, 20-workflows.env
• Added .github/env/load-env.sh script and .github/env/README.md documentation
• Updated multiple workflow files including fortress-coverage.yml, fortress-completion-tests.yml, codeql-analysis.yml, auto-merge-on-approval.yml, dependabot-auto-merge.yml, fortress-test-magex.yml, fortress-setup-config.yml, fortress-warm-cache.yml, fortress.yml, pull-request-management-fork.yml, pull-request-management.yml, scorecard.yml, stale-check.yml, and sync-labels.yml
• Updated documentation files .github/docs/workflows.md and .github/docs/repository-features.md
• Modified technical convention documents .github/tech-conventions/pre-commit.md and .github/tech-conventions/commit-branch-conventions.md

Why It Was Necessary

• The single monolithic .env.base file was difficult to maintain and understand, containing 550 lines of configuration for multiple tools and workflows
• Splitting configuration into smaller, focused files improves organization and makes it easier to locate and update specific tool configurations
• A modular environment configuration structure allows for better separation of concerns and easier debugging of configuration issues

Testing Performed

• Verified that all workflow files were updated to reference the new environment configuration structure
• Validated that the new .github/env/ directory structure contains all necessary configuration files for GoFortress tools
• Confirmed that the load-env.sh script and supporting documentation were added to facilitate the new configuration loading mechanism

Impact / Risk

• Breaking Change: Projects using the old .env.base file will need to migrate to the new modular configuration structure
• Risk Level: Medium - This is a significant refactoring of the configuration system that affects all CI/CD workflows
• Migration Required: Teams will need to update their configuration references and may need to reorganize custom configurations to align with the new structure
• Benefit: Improved maintainability and clarity of configuration management for future updates

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud