Making docker container identifier independentDescriptionCurrently, docker container is a dependent CI that has dependency on two different CIs - 'Docker engine' and 'Kubernetes Pod' (only one independent CI is used at a time). So, a docker container is identified with a combination of container Id(identifier attribute) and the independent CI(docker engine/kubernetes pod) it is related to.This leads to a possibility that duplicates are created for the same container (the container ID is same on both the CIs) because the two CIs have dependencies on two different independent CIs - 'docker engine' in case of IP-based discovery and 'Kubernetes pod' in case of serverless discovery. The fix for this PRB makes the docker container identifier independent. The docker container ID consists of 12 hexadecimal digits, which gives a total of 16 ^ 12 possibilities. So, we are looking at a very low probability of collision if we use container ID as the only identifying attribute.Steps to Reproduce 1) Run Kubernetes discovery against a server hosting kubernetes.2) Run IP based discovery on one of the nodes of the kubernetes cluster.3) Two CIs are created for the same containerWorkaroundMake the docker container identifier independent, using container id as the only identifying attribute.Related Problem: PRB1620012