chore(chart): bump to 0.4.1 to re-fire release workflow

[oren-openteams]

Summary

Bump chart/Chart.yaml version 0.4.0 → 0.4.1 so the release workflow fires again with the fixed pack-release.yaml@v1.

Context

The prior 0.4.0 chart bump attempted to trigger the release workflow but hit a bug in pack-release.yaml@v1 — the workflow's "Pin image tags to release sha" step failed for charts that don't ship any first-party (org-owned) images. No nebari-rayserve-pack-0.4.0 release was ever cut. See the failing run.

The upstream fix (nebari-dev/.github#48) is now merged, and the v1 tag has been moved to include it. But the pack-release.yaml workflow only fires on Chart.yaml version changes — so we need one more bump to trigger it. This PR is that bump.

Effect

On merge:

1. Release Chart workflow fires on the Chart.yaml change
2. Now-fixed pack-release.yaml@v1 sees empty tag-paths, skips pinning, proceeds
3. Chart gets packaged, GitHub Release nebari-rayserve-pack-0.4.1 gets created
4. Sync PR opens against nebari-dev/helm-repository

Downstream consumers (infra-atep-dev, infra-atep-cosmos) will pick up the new release automatically via their Renovate config on the next scan.

Version choice

Going 0.4.0 → 0.4.1 rather than reusing 0.4.0 because:

• Reusing an announced-but-never-cut version is fragile
• No functional chart changes between "attempted 0.4.0" and "actual 0.4.1" — a patch bump is honest signaling

Test plan

• Workflow run succeeds through all steps (Set up Helm, Package chart, Create GitHub Release, Sync to helm-repository)
• GitHub Release nebari-rayserve-pack-0.4.1 exists after merge
• A PR appears on nebari-dev/helm-repository