Top level `validate` function broken for `Path` type schema signature

The top level ValidationExtension.validate method with the Path schema signature has no current tests but it is broken:

@Function
   List<String> validate(
       final Map options = [:],
       final Object input,
       final Path schema
   ) {
       return validate(input, schema.toUri(), options)
   }

options needs to be the first parameter. However this raises another issue as toUri returns a URI object and not a string.

When I then try to use toUri().toString() I get a failing test as the path seems to be improperly resolved:

/tmp/test8497693594181044640/file:/Users/arthurgymer/workbench/nf-core/nf-schema/src/testResources/nextflow_schema_nested_parameters.json

It seems that the tmpdir is being injected in front of the real path and this is breaking things. I am not sure if this is an issue isolated to the test framework. I am not sure how to resolve this and get a working test.

Start at the top-level ValidationExtension.validate overload accepting a Path schema and inspect the existing validate overloads and test setup. Add coverage for the Path signature, checking both parameter ordering and URI/path resolution without the temporary directory being prepended. Done means the test passes for the referenced nested schema path.