feat: show warning when dependenciesMeta.{built,unplugged} is declared in non-top-level workspace

[paul-soporan]

What's the problem this PR addresses?

Just like the resolutions field, dependenciesMeta.{built,unplugged} can only be declared inside the top-level workspace manifest, but we don't currently show a warning if it is declared inside a workspace manifest.

How did you fix it?

Made it show a warning in that case.

Checklist

• I have read the Contributing Guide.

• I have set the packages that need to be released for my changes to be effective.

• I will check that all automated PR checks pass before the PR gets reviewed.

[paul-soporan]

It's really unfortunate that we can't use colors in here, but it feels wrong to pass configuration as part of an option bag parameter to Manifest.prototype.load.

[arcanis]

While I see the point, I'm not super fan of making Manifest.load aware of whether the "parsing mode" is top level or not. It feels like the CorePlugin should be the only one to decide (just like it's currently implemented), rather than adding another "return property" to the manifest class 🤔

[paul-soporan]

While I see the point, I'm not super fan of making Manifest.load aware of whether the "parsing mode" is top level or not.

It is not aware itself of the parsing mode, it just tells whatever is using it to enforce that some fields must only be declared in the top-level manifest. IMO, being aware of the parsing mode would mean passing an isTopLevel flag to manifest.load and throwing errors inside of it. This PR is trying to achieve the exact opposite.

I feel like this is the cleanest approach that still decouples the manifest parsing from the workspace that contains it.

[merceyz]

I agree with @arcanis, this seems to belong in validateWorkspace and not in the Manifest