feat(common): check dependecy in decorators

[muhabdulkadir]

Closes #<125>

Changes

• Add decorator type references on declarations and properties to the dependency graph.

Screenshots or Video

Author Checklist

• Ensure you provide a DCO sign-off for your commits using the --signoff option of git commit.
• Vital features and changes captured in unit and/or integration tests
• Commits messages follow AP format
• Extend the documentation, if necessary
• Merging to main from fork:branchname

[coveralls]

coverage: 98.763% (-0.02%) from 98.78%
when pulling acf9357 on muhabdulkadir:main
into c611435 on accordproject:main.

[muhabdulkadir]

(parent === modelFile) ? parameters.graph.addEdge(parent.getNamespace(), fqn)

This allows for a model decorated with a type reference to act as a vertex in a connected graph, causing it to be included when users search for subgraphs.

This behavior arises because we currently allow models to be decorated with type references, which implicitly suggests a composition. However, since we treat models as packages, we should avoid compositions on the packages themselves.