Split MetadataSegmentView in two implementations: caching and direct RPC call

Currently, `MetadataSegmentView` violates the Single Responsibility Principle. There should be two separate implementations of the API, one is caching and another making direct RPC, and the choice between them should be done during Dependency Injection binding.

FYI @surekhasaharan

Start by locating MetadataSegmentView and the Dependency Injection bindings that select its implementation. Trace how the current API handles caching and direct RPC calls, then identify the existing tests covering both paths. Done means the responsibilities are split into caching and direct-RPC implementations, with the choice made through dependency injection.

Written by the indexing model from the issue text.