Enable 'Format' and 'Content' assertions during schema validation

[JemDay]

Introduced more validation configuration options to apply during schema validation.

These changes have only currently been made to the query-parameter validation as a proof-of-concept, if this looks like an appropriate approach I will apply it more broadly - as such please don't merge at this time.

Included are some additional unit tests for query parameters to demonstrate the enforcement of 'date' and 'date-time' forma ts.

[codecov]

Codecov Report

Attention: Patch coverage is 95.23810% with 4 lines in your changes missing coverage. Please review.

Project coverage is 99.62%. Comparing base (3d64c93) to head (4b65d02).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
helpers/schema_compiler.go	95.55%	2 Missing ⚠️
parameters/validate_parameter.go	66.66%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #116      +/-   ##
==========================================
- Coverage   99.74%   99.62%   -0.13%     
==========================================
  Files          29       30       +1     
  Lines        3163     3194      +31     
==========================================
+ Hits         3155     3182      +27     
- Misses          8       12       +4     

Flag	Coverage Δ
unittests	99.62% <95.23%> (-0.13%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ccoVeille]

Maybe this

Suggested change

	// Sanity
	if opt != nil {
	opt(o)
	}
	if opt == nil {
	// Sanity
	continue
	}
	opt(o)

The sanity is in the nil check. The comment is misleading otherwise

[JemDay]

opted (no pun intended) to remove the comment but leave the logic as-is ... seemed more logical to me.