feat: add per-deployment resource configuration for ghost and vao

[drama17]

Summary

This PR adds the ability to configure resource constraints independently for the ghost and vao deployments in the validator chart, while maintaining backward compatibility with the global resource configuration.

Changes

• Added ghost.resources field in values.yaml for ghost deployment-specific resource constraints
• Added vao.resources field in values.yaml for vao deployment-specific resource constraints
• Updated deployment.yaml template to use ghost.resources with fallback to global.resources
• Updated deployment-vao.yaml template to use vao.resources with fallback to global.resources
• Bumped chart version from 0.4.8 to 0.4.9
• Updated README.md with documentation for new resource fields

Motivation

Previously, both ghost and vao deployments shared the same resource constraints defined in global.resources. This PR allows users to configure different resource limits and requests for each deployment independently, which is useful when:

• Ghost and vao have different resource requirements
• Fine-tuning resource allocation for better cluster utilization
• Running different workload profiles for each deployment

Backward Compatibility

This change is fully backward compatible. If ghost.resources or vao.resources are not specified, the deployments will continue to use global.resources as before.

Test Plan

• Verify chart lints successfully with `ct lint`
• Test deployment with default values (uses global.resources)
• Test deployment with ghost-specific resources
• Test deployment with vao-specific resources
• Test deployment with both ghost and vao specific resources
• Verify backward compatibility with existing configurations