Error finding file path when validating a component-definition

[CloudBeard]

Environment

Device and OS: Ubuntu 22.04
App version: v0.7.0
Kubernetes distro: N/A
Kubernetes version: N/A
provider: N/A

When validating a component-definition that imports a component-definition that contains a remote validation of a file path will error due to current file path lookup functionality and not find the validations.

Steps to reproduce

1. git clone https://github.com/defenseunicorns/uds-core.git
2. lula validate -f compliance/oscal-component.yaml
3. Check the log file to see the warning.

Expected result

assessment-result.yaml is created that contains the imported component-definition's remote validations are tested and satisfied compared to validating that component-definition individually.

Actual Result

The imported component-definition's remote validations are not found due to current file path functionality.

Visual Proof (screenshots, videos, text, etc)

Severity/Priority

Moderate/Moderate

[brandtkeller]

Should be a duplicate of #684 and should be fixed in v0.8.0 or main

[CloudBeard]

Also verified in UDS Core branch where bug was first discovered. No issues with main.

Resolved as apart of #686