Add status for the case when no links are found for links with container selectors

You currently just get something like the following:

```
spec:
appLoadStatus: LoadSuccess
node: bpfman-deployment-control-plane
programs:
- name: tc_pass_test
programId: 4399
programLinkStatus: Success
tcInfo:
links: []
type: tc
- name: tcx_next_test
programId: 4400
programLinkStatus: Success
tcxInfo:
links: []
type: tcx
```

Some rambling thoughts from a slack message:
"I agree that it would be helpful and I was thinking about it. I could probably list the links with container selectors somehow and have a status of NoContainersFound or something like that. The thing is that I get the list of expected links from getExpectedLinks() and if it doesn't find any matching containers, I just get an empty list. So, I'd have to add a pseudo link entry that just says no containers found for this link that has a container selector. But, then you'd also want to know what your container selector looked like, so maybe I could point back to the index of the link description in the BpfApplication CRD. The index might be useful for all the links in the state CRD, actually."

Start by reading getExpectedLinks() and the BpfApplication CRD link descriptions to understand how container selectors currently produce an empty list. Then inspect the state CRD representation for links and determine how a no-containers-found status and a reference to the originating link should be represented. Done means the status output distinguishes this case and identifies the relevant selector or link description.

Written by the indexing model from the issue text.