Lockfile workspace property behaves poorly in a npm workspace

[dsherret]

Given the following folder structure:

- deno.json
- package.json
- packages/package-a/package.json
- packages/package-b/package.json

If you run deno run packages/package-a/scripts/mod.ts it will resolve package.json in the packages/package-a folder and deno.json in the root folder. So the lockfile code will then be incorrectly told that the package.json dependendencies are for the most recently run package-a instead of understanding it's in an npm workspace.

To fix this, we should get Deno to understand npm workspaces beyond just for resolution with byonm, but probably a quick fix is to just not include a package.json in the "workspaces" area for now when the deno.json folder does not equal the package.json one.

Version: Deno 1.40.x