[TRB-45217] Add a new stitching attribute to kubeturbo discovered services

[SumanthKodali999]

Intent

• Adding new stitching attributes to kubeturbo discovery

Sample:

entityProperties {
    namespace: "DEFAULT"
    name: "KUBE_SYSTEM_UUID"
    value: "a67de843-6515-4dbe-9b7b-e3b148947282"
  },
  entityProperties {
    namespace: "DEFAULT"
    name: "SERVICE_NAMESPACE"
    value: "applications"
  },
  entityProperties {
    namespace: "DEFAULT"
    name: "SERVICE_NAME"
    value: "nodeport-dyna-tomcat"
  },
entityProperties {
    namespace: "DEFAULT"
    name: "DYNATRACE_SERVICE_ID"
    value: "a67de843-6515-4dbe-9b7b-e3b148947282-applications-nodeport-dyna-tomcat"
  }

Background

Changes are as follows

• Incorporated the service name, service namespace, and kube-system UID into the service_entity_dto_builder to integrate this metadata into individual entity properties.
• Added additional property with a name "DYNATRACE_SERVICE_ID" which is a combination of the 3 attributes (kube-system UID-service namespace-service name
• Developed a helper function to create these attributes for stitching.

Testing

Entity properties in the discovery response

Discovery successful

Topology Dump Entity Properties

Checklist

These are the items that must be done by the developer and by reviewers before the change is ready to merge. Please strikeout any items that are not applicable, but don't delete them

• [ ] Developer Checks
  • [ ] Full build with unit tests and fmt and vet checks
  • [ ] Unit tests added / updated
  • [ ] No unlicensed images, no third-party code (such as from StackOverflow)
  • [ ] Integration tests added / updated
  • [x] Manual testing done (and described)
  • [ ] Product sweep run and passed
  • [ ] Developer wiki updated (and linked to this description)
• [ ] Reviewer Checks
  • [ ] Merge request description clear and understandable
  • [ ] Developer checklist items complete
  • [ ] Functional code review (how is the code written)
  • [ ] Architectural review (does the code try to do the right thing, in the right way)
  • [ ] Defensive coding (incoming data checked / sanitized, exceptions logged, clear error messages)
  • [ ] No unlicensed images, no third-party code (such as from StackOverflow)
  • [ ] Security review checklist complete.

Audience

(@ mention any review/... groups or people that should be aware of this merge request)

[SumanthKodali999]

Due to the constraints in Go related to mocking objects through interface definitions, It will be challenging to mock certain concrete types such as *ClusterScraper(GetKubernetesServiceID)within the BuildDTOs function for unit testing. Additionally, transitioning to an interface might introduce complications, as certain functions remain undefined within the interface definition of ClusterScraperInterface