[processor/k8sattributes] Wait for ReplicaSet informer before starting pod informer

[bacherfl]

Description

This PR is an alternative approach to the previous fix made for #37056, which did not fully solve the issue of the deployment name not being added to a pod after the initial informer sync

Link to tracking issue

Fixes #37056

Testing

Re-enabled the flaky E2E test

[bacherfl]

after running the tests a number of times, it looks like the e2e tests are passing consistently now, so this should be ready for review

[ChrsMark]

I left some suggestions based on the following logic:

Step 1: wait for all Informers to get synced before unblocking the Pod's informer start
Step 2. Based on the waitForMetadata setting block on Pod's informer sync which is already dependent to the sync of the rest of the informers.

In this, the Pod's informer sync comes as a task chord which is the only one we need to block on from the main flow since it's already blocked on the rest "internally".

[bacherfl]

I left some suggestions based on the following logic:

Step 1: wait for all Informers to get synced before unblocking the Pod's informer start Step 2. Based on the waitForMetadata setting block on Pod's informer sync which is already dependent to the sync of the rest of the informers.

In this, the Pod's informer sync comes as a task chord which is the only one we need to block on from the main flow since it's already blocked on the rest "internally".

Thanks for the review! Those suggestions make sense, I will look into updating the PR accordingly now

[ChrsMark]

Thank's!

[ChrsMark]

@fatsheep9146 @TylerHelmuth @dmitryax could you take a look as well?

[fatsheep9146]

Why not add podInformer's HasSynced into the slice synced