Caching access token during BrowserIdcAuthPlugin authentication for subsequent/parallel session requests

Currently, running SQL queries via `BrowserIdcAuthPlugin` is done on a per-session basis. This can be tiresome when running queries across different sessions in parallel (e..g, dbt), where multiple browser pop-ups are triggered throughout the run duration. I would like to add a feature to cache the access token received during the token exchange process, so that future sessions will reuse the cached token instead of re-initializing a new session.

As the proposal involves storing the access token locally (whether it be via file/memory, plain-text/encrypted, etc.), would this be a security issue? Not sure if it would be a hard blocker before I open a PR for this feature proposal.

まず、トークン交換とセッション初期化のパスを通じて BrowserIdcAuthPlugin の認証を追跡します。キャッシュのスコープとストレージのセキュリティ要件を定義し、その後のセッションおよび並列セッションが有効なトークンを再利用し、ブラウザーのポップアップが繰り返し表示されないことを確認します。

索引モデルが issue の本文から書いたものです。