Add lan_address support in RPC and container management

- Introduced a new `lan_address` field in the RPC response for containers, allowing for easier access to UI launch URLs based on container names.
- Updated the `ContainerStatus` struct to include `lan_address`, ensuring it is initialized and passed through relevant methods in both Podman and Docker runtimes.
- Enhanced the UI store to compute enriched bundled apps with their respective `lan_address`, improving the user experience for accessing containerized applications.
- Modified the `ContainerApps` view to utilize the enriched data, ensuring the correct launch URLs are displayed for bundled apps.

core/container/src/runtime.rs

@@ -296,6 +296,7 @@ impl ContainerRuntime for DockerRuntime {
             image: parts[3].to_string(),
             created: parts[4].to_string(),
             ports: vec![],
+            lan_address: None,
         })
     }
 
@@ -367,6 +368,7 @@ impl ContainerRuntime for DockerRuntime {
                 image: container["Image"].as_str().unwrap_or("").to_string(),
                 created: container["CreatedAt"].as_str().unwrap_or("").to_string(),
                 ports,
+                lan_address: None,
             });
         }