fix(core) not finding workspace project from deep imports on enforce module boundaries

[Ryntak94]

Current Behavior

@nx/enforce-module-boundaries was not identifying the importing of an app if it was installed as a dependency in the package.json and was not listed in the paths of the tsconfig.

Also targetProjectLocator.findImportInWorkspaceProjects wasn't finding projects in the workspace if they weren't namespaced and were using subpaths.

Expected Behavior

targetProjectLocator.findImportInWorkspaceProjects should find projects even if they aren't namespaced and are using subpaths.
@nx/enforce-module-boundaries should error on importing apps even if they are not namespaced, installed as project dependencies, and don't exist in the paths of the relevant tsconfig.

Related Issue(s)

none (as far as I can tell)

Fixes #

[netlify]

✅ Deploy Preview for nx-docs canceled.

Name	Link
🔨 Latest commit	8f5cccb
🔍 Latest deploy log	https://app.netlify.com/projects/nx-docs/deploys/6998e5ea99d1d40008bde708

[netlify]

✅ Deploy Preview for nx-dev canceled.

Name	Link
🔨 Latest commit	84f18a6
🔍 Latest deploy log	https://app.netlify.com/projects/nx-dev/deploys/6998eb5a5a51260007123e63

[Ryntak94]

@FrozenPandaz Hey, I just wanted to know if this was something we could get looked at. This behavior (I believe it's a bug) is affecting our organization and I'd like to know if I should look for another solution for us (at least for now) or if we might be able to get this merged in in a reasonable amount of time.

Thanks Jason!