fix: Show deployment exposure details

[nfebe]

Show the routed service and container port in deployment details so exposure state is visible without reading service configuration.

[sourceant]

Code Review Summary

This PR enhances the deployment detail view by displaying the routed service and container port. This provides immediate visibility into the exposure state for both simple and complex deployment configurations.

🚀 Key Improvements

• Added a 'Routes to' detail row in src/views/DeploymentDetailView.vue using a new singleDomainTarget computed property.
• Unified version bump to 0.4.0-beta.7 across package.json and package-lock.json.
• Added a unit test in src/views/DeploymentDetailView.test.ts to ensure the exposure details are correctly rendered when domains are configured.

💡 Minor Suggestions

• Refactor the computed property logic to use nullish coalescing for improved safety and readability.

[sourceant]

Review complete. See the overview comment for a summary.

[sourceant]

This computed property can be refactored to improve both readability and robustness. By caching the metadata object, we avoid repeated reactive lookups of deployment.value. Additionally, switching to the nullish coalescing operator (??) is safer for optional configuration properties; it ensures that valid but falsy values (like an empty service name or a port of 0, should they ever occur in this context) are correctly handled rather than triggering an unintended fallback to global networking settings.

Suggested change

	const singleDomainTarget = computed(() => {
	const singleDomainTarget = computed(() => {
	const metadata = deployment.value?.metadata;
	const domains = metadata?.domains;
	const configured = domains?.length === 1 ? domains[0] : null;
	const service = configured?.service ?? metadata?.networking?.service;
	const port = configured?.container_port ?? metadata?.networking?.container_port;
	return service && port ? `${service}:${port}` : "";
	});