fix: Update ray-cluster karpenter_provisioner capacity-type to on-demand

[bluecrayon52]

Update ray-cluster karpenter_provisioner capacity-type to on-demand

What does this PR do?

🛑 Please open an issue first to discuss any significant work and flesh out details/direction - we would hate for your time to be wasted.
Consult the CONTRIBUTING guide for submitting pull-requests.

Motivation

The Karpenter Provisioner created for the Ray on EKS xgboost example is set to use a "spot" capacity-type, which failed to provision the required additional node. As a result, the the xgboost head node pods got stuck in a pending state. After changing the capacity-type to on-demand, a new M5a.4xlarge instance was successfully deployed and added to the ray-cluster as a node, allowing the xgboost head node pods to run.

More

• Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
• Mandatory for new blueprints. Yes, I have added a example to support my blueprint PR
• Mandatory for new blueprints. Yes, I have updated the website/docs or website/blog section for this feature
• Yes, I ran pre-commit run -a with this PR. Link for installing pre-commit locally

For Moderators

• E2E Test successfully complete before merge?

Additional Notes

[github-actions]

This PR has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this PR will be closed in 10 days

[askulkarni2]

Thanks for the fix! In the near future we will be deprecating this blueprint in the favor of an updated JARAK stack.