Prevent multiple messages for one violation

[yashincontrol]

Fixes #22. The problem is that the no-internal rule was generating duplicate error messages. This was because the rule was not correctly handling the traversal of declarations and their parents, leading to redundant checks and violation messages. Fixed the function calls and added a visitedDeclarations set to avoid duplicate processing of declarations.

re-reading

[ben-polinsky]

Looks better.
In general, the tests are a bit confusing due to the @bentley/@iTwin scope option/requirement. Could you add a comment next to the import(s) clarifying why the code is valid or invalid? Something like "not a bentley/itwin scope" or "is a local import"

[yashincontrol]

Looks better. In general, the tests are a bit confusing due to the @bentley/@iTwin scope option/requirement. Could you add a comment next to the import(s) clarifying why the code is valid or invalid? Something like "not a bentley/itwin scope" or "is a local import"

Yes, will add that

[MichaelBelousov]

lgtm, minor comments mostly formatting nits which can be resolved at your leisure

[MichaelBelousov]

Looks better. In general, the tests are a bit confusing due to the @bentley/@iTwin scope option/requirement. Could you add a comment next to the import(s) clarifying why the code is valid or invalid? Something like "not a bentley/itwin scope" or "is a local import"

Great idea, does make them much more readable.