[CORE-3183] schema registry json compatibility checks for primitive types

[andijcr]

Implementation of bool check_compatible(const json_schema_definition& reader, const json_schema_definition& writer); for string, numeric JSON types, to allow checking compatibility of a subset of JSON schema draft 4

The checking is done by traversing both schemas, looking for a rule in the writer schema that is less strict than its counterpart in the reader schema. If no such rule is found, then the result is true

Fixes: https://redpandadata.atlassian.net/browse/CORE-3183

Backports Required

• [x] none - not a bug fix
• [ ] none - this is a backport
• [ ] none - issue does not exist in previous branches
• [ ] none - papercut/not impactful enough to backport
• [ ] v24.1.x
• [ ] v23.3.x
• [ ] v23.2.x

Release Notes

• none

[andijcr]

Looks ok in principal.

1. Maybe a `std::bitset` is a nicer than a `std::set<enum>`

I went with absl::InlinedVector because performing a set difference with bitset looks a bit more obscure

[andijcr]

force push: addressed most of the review comments

• changed std::runtime_error for as_exception(invalid_schema
• simplified unit test case
• from_string_view to_string_view for json_type
• exclusiveMinimum/exclusiveMaximum simplification

[andijcr]

force push: other review comments

[andijcr]

fixed unnecessary json::Value copy in normalized_type