BUILD-8776 Improve AI migration guidelines

[matemoln]

Changes

• Remove references to get-build-number since it's bundled with the build and promote actions
• Improve documentation on build and promotion parameters
• Configure the sonar-platform parameter for build actions
• Update dependency versions

Validation

Outputs verified with VSCode and Claude Sonnet 4

Phase 2-3: Create Build and Promote Workflows

Now I'll create the main build workflow. Based on the migration guide and the Cirrus CI configuration analysis:

1. Repository visibility: This is a public repository
2. Runner selection: For public repository with auth actions → ubuntu-24.04-large
3. Artifactory roles: I found private-reader and qa-deployer patterns in the Cirrus CI config, so I need to override the default roles
4. SonarQube platform: Uses next platform (default), no override needed
5. Pull request deployment: DEPLOY_PULL_REQUEST: true is set, so I need deploy-pull-request: true and promote-pull-request: true

[sonarqubecloud]

🤖 Pull Request summary

Updates GitHub Actions migration documentation with action version bumps and workflow simplifications.

• Updates actions/checkout to v4.2.2 and jdx/mise-action to v2.4.4 throughout examples
• Removes get-build-number action references - build numbering now handled automatically
• Adds comprehensive guidance for overriding Artifactory roles and SonarQube platforms with detection matrices
• Simplifies workflow templates by removing manual build number steps
• Updates build number configuration to use SPEED portal instead of manual repository settings

Review focus: Verify the removal of get-build-number action doesn't break existing workflows and confirm the new override detection logic is accurate for different repository configurations.

💬 Please send your feedback

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