Use singleton pattern to manage Nakama client lifecycle.

[novabyte]

No description provided.

[Copilot]

Pull Request Overview

This PR introduces a singleton pattern to manage the Nakama client lifecycle in a Unity friends system, centralizing client management and reducing code duplication across the application.

• Extracts Nakama client initialization and authentication from individual controllers into a reusable singleton component
• Refactors the friends controller to use the centralized Nakama singleton instead of managing its own client instance
• Updates code style and naming conventions throughout the codebase

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
Singleton.cs	Implements generic thread-safe singleton base classes for MonoBehaviour components
NakamaSingleton.cs	Manages Nakama client lifecycle, authentication, and socket connections as a persistent singleton
NakamaFriendsController.cs	Refactored to use NakamaSingleton instead of managing its own Nakama client
FriendsRecordView.cs	Updated to use async Task pattern and naming conventions
AccountSwitcher.cs	Modified to work with the new singleton pattern for account switching functionality

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Missing space after assignment operator. Should be var deviceId = PlayerPrefs.GetString...

Suggested change

	var deviceId= PlayerPrefs.GetString("deviceId", SystemInfo.deviceUniqueIdentifier);
	var deviceId = PlayerPrefs.GetString("deviceId", SystemInfo.deviceUniqueIdentifier);