[Eno] Add inter composition ordering

[ruinan-liu]

uses dependsOn to add inter composition ordering

[ruinan-liu]

Reply to comments

[ruinan-liu]

Replied to comments

[ruinan-liu]

Respond to comment

[xiazhan]

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

[ruinan-liu]

1. DependencyStatus with CircularDependency reason is never cleared after cycle resolution
   Fixed, updated in code
2. No DependencyStatus update when dependencies aren't ready (scheduling controller logs + continues silently)
   Currently it is doing in compositionController
   // This means that dependencies exists and no synthesis started showing WaitingOnDependencies
   if len(comp.Spec.DependsOn) > 0 {
   status.Status = apiv1.WaitingOnDependenciesReason
   return status
   }
3. path.Join with empty namespace produces wrong key for standalone Compositions
   Not Applicable, there will always be a namespace
4. Circular dependency status patch errors are logged but swallowed (no requeue)
   Currently are not applicable, the scheduling controller runs on every composition/synthesizer change via SingleEventHandler, so the next reconcile will naturally retry the patch. The status will eventually converge.
5. newDependencyEventHandler predicate allows updates through but handler only enqueues on deletion
   Changed to only allow update when a composition is in deletionTimestamp given it's only used to unblock dependency deletion
6. CompositionDependency.Namespace comment says "dependent" but means "dependency" (wrong API doc)
   Done
7. Doc comment says buildComsByKey but function is named buildCompsByKey
   done. Fixed

[xiazhan]

It means ForegroundDeletion and FailOpen cannot co-exist in deleting scenario.
Good thing is that FailOpen currently is only used on reconciler level by overlay-eno-reconciler and ForegroundDeletion is not used yet.

[xiazhan]

How about ForgroundDeletion && faillingOpen case?

[xiazhan]

Why is it commented out? It looks correct.