YAML alias syntactic analysis

[char0n]

It seems that YamlAlias AST Node it not properly translated to ApiDOM. After the syntactic analysis the YamlAlias AST Node seems to be part of ApiDOM which is wrongs, as the ApiDOM shouldn't be aware of AST layer at all. This can cause various side effects in any higher level algorithms like serialization or transformation...

The goal of this issue is fix the bug and verify with simple unit test.

Refs #131

[char0n]

Architectural design

We will create a new module in https://github.com/swagger-api/apidom/tree/main/packages/apidom-ast/src/yaml called anchors-aliases. This module will have a single class ReferenceManager.

yaml
  anchors-aliases/
    ReferenceManager.ts
  errrors/
  nodes/
  schemas/

ReferenceManage will look like this to abide to YAML 1.2 nomenclature:

class ReferenceManager { 
  void addAnchor(String anchor);
  Object resolveAlias(String alias);
}

The ReferenceManager needs to be exposed from apidom-ast package and will be used in apidom-parser-adapter-yaml-1-2.

Now it's important to understand that we don't want to support anchors and aliases fully - that is part of #131. What we need now is a basic framework of anchor and alias processing, with dummy implementation.

Now what does the dummy implementation mean? Inside the apidom-parser-adapter-yaml-1-2 package when YamlAnchor node is intercepted, we'll store it by using ReferenceManager.prototype.addAnchor. Then when YamlAlias node is intercepted, we'll run it through the ReferenceManager.prototype.resolveAlias. Now the resolveAlias will have very simple implementation which will basically return the string value of the alias node: node.content. We will not do any resolution for now.

[char0n]

Addressed in #3785