FDN-4363: Migrate from Kaniko to BuildKit

[nicolagi]

Summary

• Add buildkit: true flag to mainJenkinsBuildArgo() call to migrate Docker image builds from Kaniko to BuildKit
• BuildKit resource limits added where custom Kaniko resources were configured (roughly half the Kaniko values)

Test plan

• PR branch builds will still use Kaniko (BuildKit activates on merge to main)
• Monitor first build after merge to confirm BuildKit succeeds
• Verify image is pushed to ECR correctly

🤖 Generated with Claude Code

Summary by CodeRabbit

Release Notes

• Chores
  • Updated internal build configuration.

---

Note: This release contains no user-facing changes.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new buildkit: true parameter is added to the mainJenkinsBuildArgo function call in the Jenkinsfile, expanding the named arguments passed to this build configuration routine.

Changes

Cohort / File(s)	Summary
Jenkins Build Configuration Jenkinsfile	Added buildkit: true parameter to the mainJenkinsBuildArgo call, enabling BuildKit support in the build pipeline.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding a buildkit: true flag to migrate Docker image builds from Kaniko to BuildKit in the Jenkinsfile.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[flow-tech]

Click here for code coverage report: https://jenkins.flo.pub/job/flowcommerce/job/dependency/job/PR-890/1/scoverage-report/