Please address the comments from this code review:
## Overall Comments
- Consider moving the hard-coded status.displayName strings into your l10n resources to support localization instead of using English literals.
- Unify the UI status display by using ContainerStatus.displayName for DockerPs items as well (instead of raw state) so both Docker and Podman show statuses consistently.

## Individual Comments

### Comment 1
<location> `lib/data/model/container/status.dart:53` </location>
<code_context>
+  }
+
+  /// Get display string for the status
+  String get displayName {
+    return switch (this) {
+      ContainerStatus.running => 'Running',
</code_context>

<issue_to_address>
Hardcoded display names may limit localization support.

Consider using a localization mechanism for displayName to support multiple languages if your app requires internationalization.

Suggested implementation:

```
  /// Get localized display string for the status
  String displayName(BuildContext context) {
    final localizations = AppLocalizations.of(context);
    return switch (this) {
      ContainerStatus.running => localizations.containerStatusRunning,
      ContainerStatus.exited => localizations.containerStatusExited,
      ContainerStatus.created => localizations.containerStatusCreated,
      ContainerStatus.paused => localizations.containerStatusPaused,
      ContainerStatus.restarting => localizations.containerStatusRestarting,
      ContainerStatus.removing => localizations.containerStatusRemoving,
      ContainerStatus.dead => localizations.containerStatusDead,
      ContainerStatus.unknown => localizations.containerStatusUnknown,
    };
  }

```

1. You must add the corresponding keys (e.g., `containerStatusRunning`, `containerStatusExited`, etc.) to your `intl` ARB files and regenerate your localization classes.
2. Update all usages of `displayName` to pass a `BuildContext` parameter, e.g., `status.displayName(context)`.
3. Ensure `AppLocalizations` is imported: `import 'package:flutter_gen/gen_l10n/app_localizations.dart';`
</issue_to_address>

### Comment 2
<location> `lib/view/page/container/container.dart:223` </location>
<code_context>
-              final PodmanPs ps => ps.running ? l10n.running : l10n.stopped,
-              final DockerPs ps => ps.state,
+              final PodmanPs ps => ps.status.displayName,
+              final DockerPs ps => ps.state ?? ps.status.displayName,
             }}',
             style: UIs.text13Grey,
</code_context>

<issue_to_address>
Fallback to displayName may cause inconsistent UI if state is not localized.

Ensure both ps.state and ps.status.displayName are consistently localized to avoid mismatched or untranslated status values in the UI.

Suggested implementation:

```
            '${item.image ?? l10n.unknown} - ${switch (item) {
              final PodmanPs ps => l10n.localizeStatus(ps.status.displayName),
              final DockerPs ps => l10n.localizeStatus(ps.state ?? ps.status.displayName),
            }}',

```

If `l10n.localizeStatus` does not exist, you need to implement it in your localization class. It should accept a status string and return the localized version, falling back to the original string if no translation is available. Example:

```dart
// In your l10n class
String localizeStatus(String status) {
  switch (status) {
    case 'Running':
      return running; // already localized
    case 'Stopped':
      return stopped; // already localized
    // Add other status cases as needed
    default:
      return status;
  }
}
```
Make sure to update the localization files if you add new status values.
</issue_to_address>