feat (apidom-ls): Change error message for type linting rules

[damian-polewski-sb]

This PR changes the error messages for type linting rules for OpenAPI 3.0.x, OpenAPI 3.1, AsyncAPI 2.0, and AsyncAPI 2.1-2.6 to include the information about allowed values for the type field.

Description

This PR does the following:

• Changes error messages for OpenAPI 3.0.x, OpenAPI 3.1, AsyncAPI 2.0, and AsyncAPI 2.1-2.6

Motivation and Context

This change is required to solve this ticket (SWG-8486) found during OpenAPI 3.1 bug bash. It has been decided that it would be better to include information about what are the allowed values for type field.

How Has This Been Tested?

This PR only changes error message text so there are no changes in the package behavior.

Screenshots (if appropriate):

Checklist

My PR contains...

• No code changes (src/ is unmodified: changes to documentation, CI, metadata, etc.)
• Dependency changes (any modification to dependencies in package.json)
• Bug fixes (non-breaking change which fixes an issue)
• Improvements (misc. changes to existing features)
• Features (non-breaking change which adds functionality)

My changes...

• are breaking changes to a public API (config options, System API, major UI change, etc).
• are breaking changes to a private API (Redux, component props, utility functions, etc.).
• are breaking changes to a developer API (npm script behavior changes, new dev system dependencies, etc).
• are not breaking changes.

Documentation

• My changes do not require a change to the project documentation.
• My changes require a change to the project documentation.
• If yes to above: I have updated the documentation accordingly.

Automated tests

• My changes can not or do not need to be tested.
• My changes can and should be tested by unit and/or integration tests.
• If yes to above: I have added tests to cover my changes.
• If yes to above: I have taken care to cover edge cases in my tests.
• All new and existing tests passed.

[char0n]

LGTM. Thanks for contributing!