feat: link kubernetes LB services to AWS ELB

[adityathebe]

## fix source vertex not found error by namespacing all look ups to the scraper.

The source vertex not found error would occur only in cases where multiple clusters were being scraped. The lookups needed to be scoped to the given scraper.

Example: When forming a Namespace default -> Deployment Nginx relationship for cluster A, the lookup for external id Kubernetes/Namespace//default would return the ID of the default namespace from cluster B. This would cause failure when forming the graph as the edge couldn't be inserted since there's no source vertex in the graph.

resolves: #703

[moshloop]

@adityathebe - Not sure we can force this - There will be instances of cross-scraper relationships

e.g

• a Flux object in a management cluster creating resources in a target cluster without a flux relationship
• A change being detected in 1 scraper being assigned to a config scraped elsewhere

I think the problem is using Kubernetes/Namespace/%s as an ExternalID - which it shouldn't be - external ids should be globally unique - ideally even across all config types e.g. with a FQDN or a UID.

I think we just need to change https://github.com/flanksource/config-db/blob/main/scrapers/kubernetes/kubernetes.go#L438 to use the resourceIdMap

[adityathebe]

I think we just need to change https://github.com/flanksource/config-db/blob/main/scrapers/kubernetes/kubernetes.go#L438 to use the resourceIdMap

The problem is that on incremental scrapes, the resource id map is nil. Or at least, we cannot guarantee that the namespace or possibly other parents as well are going to be in the resource id map.

I'll create a separate issue for this.

[github-actions]

🎉 This PR is included in version 0.0.372 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀