Investigate Performance of bpfman agent

We've seen the sample BpfApplication CRD take ~30 seconds to finish loading its eBPF programs. A look at the agent log suggests that this biggest factor is the call to bpfman to load the programs, which appears to take from 2-12 seconds. So, while this issue is being written against bpfman-operator, I believe that the first place to look is in the bpfman load path.

Some likely suspects are the image pull from podman and cosign validation, but this needs to be confirmed.

Start with the sample BpfApplication CRD loading flow and the agent logs, then trace the bpfman load path. Measure the time spent loading programs and separately investigate the suspected podman image pull and cosign validation steps; done means identifying and documenting the confirmed bottleneck.

Written by the indexing model from the issue text.