Fix custom schema validation

[garrettmflynn]

fix #634

There's some custom schema validation logic that wasn't referring to the correct schema. Fixed!

[CodyCBakerPhD]

@garrettmflynn This prevents the flag from raising on entry to the field, but I can't move past the file metadata page due to the same previous schema error

[garrettmflynn]

Can you try again? This is working fine on my end.

Avoided a stray error in the Search component with the last push. May have something to do with what you observed

[CodyCBakerPhD]

Can you try again? This is working fine on my end.

I'm surprised; after digging into this it was coming from the neuroconv metadata schema validation

I opened catalystneuro/neuroconv#769, which fixed it for me when using this branch

I know we've had issues/differences with the jsonschema python library on Mac - maybe mine is a Windows specific issue?

[garrettmflynn]

Huh weird. Since this is the pattern used to check the validity of the value, we shouldn't receive any errors regarding the enum field, though, right?

[CodyCBakerPhD]

we shouldn't receive any errors regarding the enum field, though, right?

I might not have read the error from the popup window closely enough; only digging through the traceback led me to the source and the right message

[CodyCBakerPhD]

This works for me now

[CodyCBakerPhD]

Also, any way to write a test for this?

[garrettmflynn]

This one is much more straightforward than the others. I'll start with this next week.

[CodyCBakerPhD]

Pydantic v2 issues causing CI failure should be fixed with the pin to pyinstaller hook contrib + catalystneuro/neuroconv#770

Ref; pyinstaller/pyinstaller-hooks-contrib#610