Feat: Add YAML validation for compose content in deployment flows

[austin047]

• Add a method to validate compose Yaml
• Use validation in NewDeploymentModal and DeploymentDetailView before submission

[sourceant]

Code Review Summary

This PR introduces YAML syntax validation for Docker Compose content before it is sent to the backend. It also includes UI improvements for password fields and updates the environment configuration.

🚀 Key Improvements

• Added yaml package for client-side parsing.
• Implemented a central validateComposeYaml utility.
• Added password visibility toggles in the deployment modal.
• Integrated validation into NewDeploymentModal and DeploymentDetailView.

💡 Minor Suggestions

• Enable unique key checking in YAML parser.
• Consider a reusable component for password inputs.

[sourceant]

Review complete. See the overview comment for a summary.

[sourceant]

By default, the yaml package's parse function might only throw for critical syntax errors. For stricter validation (e.g., catching duplicate keys which are common in Compose files), it is better to check for warnings or use a stricter parsing configuration if available in the version installed.

Suggested change

	parse(trimmed);
	parse(trimmed, { uniqueKeys: true });

[sourceant]

The API URL has been changed from port 8080 to 8090 and appended with /api. Ensure this change is intentional for the example environment and matched in server-side configurations.

Suggested change

	VITE_API_URL=http://localhost:8080
	VITE_API_URL=http://localhost:8090/api