Make iiif-net parse all the Manifests in the Cookbook

[tomcrane]

The IIIF Cookbook:
https://theseus-viewer.netlify.app/cookbook-collection.json
https://iiif.io/api/cookbook/

1. Biggest change here is renaming Audio to Sound (the latter is correct in the spec). I considered just using the string but it breaks the pattern of using nameof to when comparing type values.
2. This needed quite a few tweaks to custom JSON converters and a new ISource and ISourceConverter for SpecificResource
3. Added SvgSelector

When I ran the full test suite there were loads of breaking tests - but they all seem to be string comparisons of expected and actual JSON, when the JSON is actually equivalent.

In the PMC work I used this quite a bit:
https://github.com/lateapexearlyspeed/Lateapexearlyspeed.JsonSchema?tab=readme-ov-file#lateapexearlyspeedxunitassertionjson

(see JsonAssertion.Equivalent)

Should we use something like that?

[donaldgray]

When I ran the full test suite there were loads of breaking tests - but they all seem to be string comparisons of expected and actual JSON, when the JSON is actually equivalent.

In the PMC work I used this quite a bit:
https://github.com/lateapexearlyspeed/Lateapexearlyspeed.JsonSchema?tab=readme-ov-file#lateapexearlyspeedxunitassertionjson

(see JsonAssertion.Equivalent)

Should we use something like that?

I suspect the issue is down to line endings. I added a actual.ShouldMatchJson(expected); helper but it's only used in a few places, and it's a bit rough, so sounds like that lib would help