feat: Add connection state check method

[kirre-bylund]

Summary

Adds CheckConnectionStatus — a single public method that reports the current connection and session state for a player without requiring the developer to interpret raw HTTP status codes.

Implementation of https://github.com/lootlocker/index/issues/1574 for the Unity SDK

How it works

1. Fast local checks (no network call):

   • SDK not initialized → NotInitialized
   • No session token in local state → NotSignedIn
   • Application.internetReachability == NotReachable → NoConnection

2. Live check (ping):

   • 200 → SignedInAndConnected (+ ServerTime populated)
   • 5xx → ServerError
   • 401 or 403 → calls GetPlayerBanStatus to disambiguate:
     • is_banned == true → Banned (+ BanDetails populated)
     • otherwise → SessionExpired
   • No response / timeout / status 0 → NoConnection

Both 401 and 403 trigger the ban-status check because allowTokenRefresh=true can cause a ban-related 403 to auto-refresh, fail, and surface as a synthesized 401.

The method never attempts token refresh — it reports raw state so the developer can decide how to recover.

API

LootLockerSDKManager.CheckConnectionStatus(response =>
{
    switch (response.State)
    {
        case LootLockerConnectionState.SignedInAndConnected: /* all good */ break;
        case LootLockerConnectionState.NotSignedIn:         /* prompt login */ break;
        case LootLockerConnectionState.SessionExpired:      /* refresh or re-auth */ break;
        case LootLockerConnectionState.Banned:              /* show response.BanDetails */ break;
        case LootLockerConnectionState.NoConnection:        /* show offline UI */ break;
        case LootLockerConnectionState.ServerError:         /* retry later */ break;
        case LootLockerConnectionState.NotInitialized:      /* init SDK first */ break;
    }
}, forPlayerWithUlid: null); // optional, defaults to active player

[Copilot]

Pull request overview

Adds a new public API (LootLockerSDKManager.CheckConnectionStatus) to report a player’s connection/session state (initialized, signed in, banned, no connection, etc.) without requiring developers to interpret HTTP status codes directly.

Changes:

• Introduces LootLockerConnectionState and LootLockerConnectionStateResponse response models.
• Adds a new LootLockerAPIManager.CheckConnectionStatus request implementation using ping (+ ban status disambiguation for 401/403).
• Adds the public LootLockerSDKManager.CheckConnectionStatus facade with fast local checks (initialized/session token/internet reachability) before the live ping.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
Runtime/Game/Requests/MiscRequests.cs	Adds the connection state enum/response model and the underlying ping + ban-status request logic.
Runtime/Game/LootLockerSDKManager.cs	Adds the public CheckConnectionStatus API and local preflight checks before calling the request layer.

[JohannesLoot]

Awesome stuff!
Merge away!