Summary: Implement automated service dependency detection and mapping within the Harness IDP (Internal Developer Portal) to reduce manual overhead.

Description: Current Behavior:

Users must manually define relationships (upstream/downstream dependencies) between components in the IDP.

This manual process is time-consuming and prone to errors..

The team is currently manually adding relations for ~94-100 components.

Desired Behavior:

The IDP should automatically detect and map service dependencies based on code analysis, traces, or existing integrations

Example Scenario: If Service B calls Service A and Service C, the system should automatically populate these relationships in Service B's dependency view without manual input.

The visualization should clearly show call chains (e.g., "Partner Notification calls Automation Client API, which calls Automation HMS API").