Please address the comments from this code review:

## Overall Comments
- The `_serialize_pydantic` wrapper only handles a single `BaseModel` or `dict`; if any existing resources return lists or nested structures of Pydantic models, you may want to extend this helper to recursively serialize common container types (e.g., list/tuple/dict of models) to avoid subtle runtime issues.
- By placing `_serialize_pydantic` as the outermost wrapper before `log_execution` and `telemetry_resource`, those middle layers now see only JSON strings rather than structured models; consider whether these wrappers should instead operate on the original `BaseModel` (e.g., for richer logging/metrics) and apply serialization only at the final FastMCP boundary.

## Individual Comments

### Comment 1
<location path="MCPForUnity/Editor/Windows/Components/Advanced/McpAdvancedSection.cs" line_range="47-50" />
<code_context>
         public event Action OnGitUrlChanged;
         public event Action OnHttpServerCommandUpdateRequested;
         public event Action OnTestConnectionRequested;
+        public event Action OnPackageDeployed;

         public VisualElement Root { get; private set; }
</code_context>
<issue_to_address>
**suggestion:** Event name may be misleading since it also fires on restore.

Since this event is raised for both deploy and restore, the name doesn’t reflect its full behavior. Consider renaming it to something more generic (e.g., `OnPackageChanged`) or adding distinct events for deploy and restore so subscribers can clearly distinguish the operation.

Suggested implementation:

```csharp
        public event Action OnGitUrlChanged;
        public event Action OnHttpServerCommandUpdateRequested;
        public event Action OnTestConnectionRequested;

        /// <summary>
        /// Raised whenever the package deployment state changes (deploy or restore).
        /// </summary>
        public event Action OnPackageChanged;

        /// <summary>
        /// Raised specifically after a successful package deployment.
        /// </summary>
        public event Action OnPackageDeployed;

        /// <summary>
        /// Raised specifically after a successful package restore.
        /// </summary>
        public event Action OnPackageRestored;

```

```csharp
            else
            {
                EditorUtility.DisplayDialog(
                    "Deployment Complete",
                    result.Message + (string.IsNullOrEmpty(result.BackupPath) ? string.Empty : $"\nBackup: {result.BackupPath}"),
                    "OK");

                // Notify listeners of a successful deployment and a package state change.
                OnPackageDeployed?.Invoke();
                OnPackageChanged?.Invoke();
            }

```

To fully implement the intent of your review comment, you should also:
1. Locate the code path that performs a **restore** operation in `McpAdvancedSection` (or related classes in this editor window) and:
   - Replace any existing `OnPackageDeployed?.Invoke()` call that is used for restore with:
     - `OnPackageRestored?.Invoke();`
     - `OnPackageChanged?.Invoke();`
2. Update any external subscribers:
   - If any code currently relies on `OnPackageDeployed` to be fired for restore, adjust those subscribers to:
     - Listen to `OnPackageChanged` when they don’t care which operation occurred, **or**
     - Listen to `OnPackageDeployed` and/or `OnPackageRestored` when they need to distinguish between deploy and restore.
This will ensure the event naming is no longer misleading while giving callers explicit hooks for both operations.
</issue_to_address>