feat: webhook to set agent injection env var with odigos additions

[tamirdavid1]

This is the initial phase of enabling the webhook to set agent injection-related environment variables (e.g., PYTHONPATH). The plan is to merge this after the migration and the new runtime inspection have been running for a while.

Once enough time has passed, I will merge this change to handle simpler cases where the envOverwriter is not involved. After this phase runs for a sufficient period, we can fully remove the envOverwriter and rely solely on this logic.

Finally, we can clean up the remaining code related to the envOverwriter.

[blumamir]

We usually host these sort of functions in k8sutils. WDYT?

[tamirdavid1]

As we discussed let's discuss on this with @RonFed and take decision here

[RonFed]

I'm OK with both options as long we don't have duplicated functions in more than one place.
It feels like we have a lot of functions like this in

odigos/instrumentor/instrumentation/instrumentation.go

Line 157 in 0bf1896

func getLanguageOfContainer(runtimeDetails []odigosv1.RuntimeDetailsByContainer, containerName string) common.ProgrammingLanguage {

odigos/instrumentor/instrumentation/instrumentation.go

Line 167 in 0bf1896

func getContainerOtherAgents(runtimeDetails []odigosv1.RuntimeDetailsByContainer, containerName string) *odigosv1.OtherAgent {

odigos/instrumentor/instrumentation/instrumentation.go

Line 178 in 0bf1896

func getLibCTypeOfContainer(runtimeDetails []odigosv1.RuntimeDetailsByContainer, containerName string) *common.LibCType {

[RonFed]

I'm OK with both options as long we don't have duplicated functions in more than one place.
It feels like we have a lot of functions like this in

odigos/instrumentor/instrumentation/instrumentation.go

Line 157 in 0bf1896

func getLanguageOfContainer(runtimeDetails []odigosv1.RuntimeDetailsByContainer, containerName string) common.ProgrammingLanguage {

odigos/instrumentor/instrumentation/instrumentation.go

Line 167 in 0bf1896

func getContainerOtherAgents(runtimeDetails []odigosv1.RuntimeDetailsByContainer, containerName string) *odigosv1.OtherAgent {

odigos/instrumentor/instrumentation/instrumentation.go

Line 178 in 0bf1896

func getLibCTypeOfContainer(runtimeDetails []odigosv1.RuntimeDetailsByContainer, containerName string) *common.LibCType {

[damemi]

Would you please update the test cases re:reported-name like I did in 8b60b1d ? You can probably just cherry pick that commit

[tamirdavid1]

Would you please update the test cases re:reported-name like I did in 8b60b1d ? You can probably just cherry pick that commit
Yea I can do that, can you elaborate about why 26 spans reduced to 13?

[damemi]

Yea I can do that, can you elaborate about why 26 spans reduced to 13?

The original test used the same resource names for 2 runs of traffic generation. So the first time it would generate 13 spans and then 13 more. But now the test updates the reported-name after the first set is generated, so the new set of spans is just 13 entirely new resources.

[tamirdavid1]

Yea I can do that, can you elaborate about why 26 spans reduced to 13?

The original test used the same resource names for 2 runs of traffic generation. So the first time it would generate 13 spans and then 13 more. But now the test updates the reported-name after the first set is generated, so the new set of spans is just 13 entirely new resources.

Done, the requested commit has been cherry-picked.