[api-extractor] Error when imported types are used in `@public`-like interfaces but their library is not declared as a `peerDependency` or `dependency`

[TheLarkInn]

Summary

In the case of this bug: #3844

If a type is imported from an installed library, and that library is not declared as a dependency/peerDependency, api-extractor should error/throw when the user attempts to use it in any @public-like interfaces.

Repro steps

1. Library uses api-extractor to create typings
2. Library imports a libraries types into their code
3. Library uses that type in an @public-like interface

Expected result:
api-extractor should throw, and then inform the user that they are attempting to use a type/import of a package that is not declared as a dependency/peerDependency in an @import-like interface.

Actual result:
api-extractor does not throw, and allows a user to publish anyways

Then bugs like these (#3844) happen less often.

[TheLarkInn]

cc @zelliott on your thoughts here also.