fix(trait): preserve kamelet ConfigMaps during dry-build BuildComplete phase

[pkalsi97]

Closes #6422

Summary

When we run kamel run --dont-run-after-build, the operator:

1. Builds the integration kit
2. Stops at BuildComplete phase instead of deploying
3. Waits for you to explicitly call kamel deploy later

Problem

When an Integration/Pipe uses kamelets (like timer-source, log-sink), the operator creates ConfigMaps containing the kamelet templates:

<integration-name>-kamelet-timer-source-template
<integration-name>-kamelet-log-sink-template

But because of current gc behaviour: Any time an integration is in BuildComplete → run GC → delete ConfigMaps.

if e.Integration.GetGeneration() > 1 || e.IntegrationInPhase(v1.IntegrationPhaseBuildComplete) {
    // Run garbage collection - delete resources
}

The old code treated both Dry Build and Undeploy the same → always deleted resources.

Solution:

Dry-build → Replicas = nil → Skip GC → ConfigMaps preserved
Undeploy → Replicas > 0 → Run GC → Runtime resources cleaned up

BEFORE FIX:
  dry-build → BuildComplete → GC runs → ConfigMaps DELETED → deploy FAILS
AFTER FIX:
  dry-build → BuildComplete → Replicas=nil → Skip GC → ConfigMaps KEPT → deploy WORKS
  undeploy  → BuildComplete → Replicas>0  → Run GC   → Cleanup WORKS

[github-actions]

✔️ Unit test coverage report - coverage increased from 51.6% to 51.7% (+0.1%)

[pkalsi97]

Changes I have made after feedback

1. Add hasNeverDeployed() - Uses two checks, DeployTimestamp and Ready condition's FirstTruthyTime
2. Added some unit test
3. Added an extra e2e test to ensure this works reliably.

[github-actions]

✔️ Unit test coverage report - coverage increased from 51.6% to 51.7% (+0.1%)