…ther drives in Windows. For more details, see open-policy-agent#6910 and open-policy-agent/conftest#979.

OPA should be capable of accessing Rego policies from specified paths including drives (e.g., c:\a\b\c.rego).

The code has been updated to allow OPA to load Rego policies from paths with drives. Now, OPA can load Rego policies from paths, URLs, and drives.

Fixes open-policy-agent#6910

Signed-off-by: pckvcode <pck@veracode.com>

…nput sources:

Existing Inputs:
1. Absolute file paths (e.g., /a/b/c/example.rego)
2. Paths with URLs (e.g., file:///path/to/file.json)
3. Paths with drive letters and URLs (e.g., "C:file:///C:/a/b/c")

New Inputs:
1. Paths with drive letters (e.g., C:\a\b\c\example.rego)

This requirement ensures that Opa can handle a variety of input formats, including local file paths, remote URLs, and even mixed formats that include both drive letters and URLs.

open-policy-agent#6910
Signed-off-by: pckvcode <pck@veracode.com>

…clude a Windows drive letter (e.g., C:\a\b\c\example.rego). When tests are run on Windows, temporary directories are created on the C drive (e.g., C:\Users\<username>\AppData\Local\Temp).

Fixes: open-policy-agent#6910

Signed-off-by: pckvcode <pck@veracode.com>

Signed-off-by: pckvcode <pck@veracode.com>