Feature Request: Expose explicit controls for account state caching and refresh behavior

### Is your feature request related to a problem? Please describe.

_No response_

### Describe the solution you'd like

## Overview

1. The Account SDK manages account-related data internally, but developers do not have clear visibility or control over when cached state is reused versus when fresh data is fetched. Making this behavior more explicit would improve predictability and flexibility.

## Problem Description

2. Without explicit controls, developers must infer caching behavior or implement their own refresh logic around the SDK. This can lead to unnecessary network calls or incorrect assumptions about data freshness.

## Expected Behavior

3. Developers should be able to clearly understand and influence when account state is cached or refreshed, without relying on undocumented internal behavior.

## Proposed Solution

4. Expose explicit APIs or configuration options that allow developers to control caching and refresh behavior, such as forcing a refresh or specifying cache lifetimes.

### Describe alternatives you've considered

_No response_

### Additional context

_No response_

The issue names no files, tests, or entry points. Start by mapping where the Account SDK caches and refreshes account state, then clarify the API or configuration contract for forced refreshes and cache lifetimes. Done means developers can explicitly control and understand cache reuse versus fresh fetches.

Written by the indexing model from the issue text.