fix(registry): schema conformance

[sambacha]

Fix the usage of exclusiveMinimum

Description

for the “chainId”, “blocks.estimateBlockTime”, “grpcUrls.concurrency”, “retry.maxRequests”, and “retry.baseRetryMs”), the keyword exclusiveMinimum is given a numeric value. In JSON Schema draft‑07 the exclusiveMinimum keyword is of type boolean, and is used with a separate minimum value as this enforces a strict inequality.

Backward compatibility

Technically, no as there was no strict inequality per se defined.

Testing

YMMV

[changeset-bot]

⚠️ No Changeset found

Latest commit: d766279

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR