fix: prevent silent ancestor resolution from malformed YAML paths

[willbuckner]

Fixes #5979

When malformed YAML creates resource paths like "../../base - ../../shared/prod", FileLoader.New() was silently resolving these to existing ancestor directories through path normalization instead of failing appropriately. This could cause resources to be loaded from unintended locations, which can be especially dangerous in CI/CD environments.

Added validation in FileLoader.New() to check directory existence before allowing path normalization, preventing the silent "ancestor snapping" behavior.

Before:

=== RUN   TestNewLoaderMalformedPath
    fileloader_test.go:223:
        	Error Trace:	/Users/wbuckner/dev/kustomize/api/internal/loader/fileloader_test.go:223
        	Error:      	"must build at directory: not a valid directory: '/shared/prod' doesn't exist" does not contain "does not exist"
        	Test:       	TestNewLoaderMalformedPath
--- FAIL: TestNewLoaderMalformedPath (0.00s)
FAIL
FAIL	sigs.k8s.io/kustomize/api/internal/loader	0.757s
FAIL

After:

=== RUN   TestNewLoaderMalformedPath
--- PASS: TestNewLoaderMalformedPath (0.00s)
PASS
ok  	sigs.k8s.io/kustomize/api/internal/loader	(cached)

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: willbuckner / name: Will Buckner (0767f90)

[k8s-ci-robot]

Welcome @willbuckner!

It looks like this is your first PR to kubernetes-sigs/kustomize 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/kustomize has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @willbuckner. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: willbuckner
Once this PR has been reviewed and has the lgtm label, please assign koba1t for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[koba1t]

/ok-to-test

[koba1t]

Hi @willbuckner
I think this PR is worth introducing.

Please fix tests that happen on CI.