Feat: Unify source of data for complex operations

### What would you like to be added?

Currently audit and scoring apis are getting resource details from Karpor storage such as ElasticSearch, in the form of manifests.
Topology api is getting data from the spoke clusters.
They should be unified.

### Why is this needed?

The source of the data should be the same one (either Karpor storage or source clusters) depending on the assumptions made on how data is synced back to Karpor.

Start by tracing the audit, scoring, and topology APIs and documenting where each currently reads resource details. Resolve whether Karpor storage or the spoke clusters is authoritative based on how data is synced back to Karpor. Done means all three APIs use the same agreed source.

Written by the indexing model from the issue text.