fix(oas): change how exclusiveMin & Max are handled

[brendarearden]

Motivation and Context

As part of supporting OAS 3.1 exporter, I noticed that exclusiveMinimum and exclusiveMaximum values were not being preserved. Since we handle changing this behavior with the drafts, it makes sense to preserve these values during the http spec process

Reminder: OAS3 - exclusiveMin / Max are booleans OAS3.1 - exclusiveMin / Max are integers

https://github.com/stoplightio/platform-internal/issues/15265

Description

check to see if value is a number and do not delete from schema if it is

How Has This Been Tested?

added test to capture exclusiveMin / Max with integer value yarn test locally yalc'd into platform internal and confirmed that all exporter tests (oas2, 3, 3.1) are passsing

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• [x] This PR's code follows as closely as possible the coding style/guidelines of this project.
• [x] I have added error reporting and followed the error reporting guidelines.
• [x] I have added event tracking and followed the event tracking guidelines.
• [x] I have updated any relevant documentation accordingly to reflect this PR's changes.
• [x] I have added automated tests (unit/integration/e2e/other) to cover my changes.
• [x] All new and existing tests pass locally (excluding flaky CI tests).

[stoplight-bot]

:tada: This PR is included in version 5.6.2 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: