fix: correct wrong behavior of the key property named deprecated (#626)

[BatLeDev]

This pull request introduces changes to handle the deprecated property in JSON schemas more effectively. The main updates include modifications to the validation logic, test snapshots, and end-to-end tests.

Handling deprecated property:

• src/validator.ts: Added a check to ensure that if deprecated is present in properties, it returns true, allowing the schema validation to pass.

Test updates:

• test/__snapshots__/test/test.ts.md: Updated the snapshot to include the deprecated property in the expected output.
• test/e2e/deprecated.ts: Added a new test case for the deprecated property, including a default value and type definition.

Spec OpenAPI

According to the OpenAPI 3.1 specification, the deprecated property is a valid keyword in schemas and operation objects. This update ensures that the validation logic properly recognizes deprecated as a legitimate property, preventing unnecessary errors when processing OpenAPI-compliant JSON schemas.

Reference: OpenAPI 3.1 Specification - Operation Object

fix #626

[valerii15298]

@bcherny can this be merged? Changes seem to be valid and it would resolve a bug with deprecated keyword being as a property?