[FEATURE]: Improved GitHub API Fetching with IndexedDB Caching

### Feature and its Use Cases

## What does it do??
This update adds a browser-side caching layer using IndexedDB for GitHub API responses. The cache stores organization, repository, contributor, issue, and rate-limit data for a limited time, reducing repeated API calls and improving app responsiveness.

The update also improves the GitHub fetch flow by handling rate-limit information, supporting optional Personal Access Tokens, and reusing cached responses when valid data is already available.

## What is the feaure
The feature is a client-side API caching and fetch optimization system for the Org Explorer app.

It includes:
- IndexedDB-based cache storage.
- One-hour cache expiration using TTL.
- Cached reads before making GitHub API requests.
- Automatic cache writes after successful API responses.
- GitHub rate-limit updates through a custom browser event.
- Support for authenticated requests using a Personal Access Token.
- Shared fetch logic through fetchWithCache.

## Benefit
Users benefit because the app becomes faster, more stable, and more efficient.

### Additional Context

_No response_

### Code of Conduct

- [x] I have joined the [Discord server](https://discord.gg/hjUhu33uAn) and will post updates there
- [x] I have searched existing issues to avoid duplicates

The issue names no files, tests, or entry points. Start by locating the app’s GitHub API fetch flow and determine where organization, repository, contributor, issue, and rate-limit data are read and written; done means valid one-hour IndexedDB reuse, successful-response writes, rate-limit events, and optional token requests work.

由索引模型根據 Issue 內容生成。