feat: configurable processing of circular reference

[412b]

Description
This PR address missing feature/support of circular references in any way.
Intent is to keep default behavior as close as possible to previous one unless cases, when specific option is provided to handle circular references.

Related issue(s)
Resolves #201

[github-actions]

Welcome to AsyncAPI. Thanks a lot for creating your first pull request. Please check out our contributors guide useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[412b]

@Souvikns @aeworxet please take a look. docs to be updated, when the conceptual approach is accepted.
there are, of course, some drawbacks/compromises here, which are consequences of missing features in json-schema-ref-parser.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Souvikns]

does @asyncapi/parser accepts this as a valid schema, can you validate it and comment the output.

[aeworxet]

This PR is not relevant at this time.

The NPM package @apidevtools/json-schema-ref-parser was updated to v14.2.1 to include the required functionality in #214.

Support for Node.js versions earlier than v24 was removed in #216, resulting in the release of MAJOR version 1.0.1.

A waiting period for users to adopt these changes is currently in effect.