[Meteor 3] Fix how to compare constraints version when publishing a package

[denihs]

We had reports that people weren't able to deploy packages because they were getting the error:

inconsistent dependency constraint across unibuilds?

Debugging further, I could check that here, d.constraint and use.constraint were never equal if using api.versionsFrom with conditioning versions for a package, like '[email protected]||2.0.0-beta300.7'.

What I'm doing on this PR is to verify if the package constraint version is available in the specified Meteor version determined by api.versionsFrom.

[netlify]

✅ Deploy Preview for v3-meteor-api-docs canceled.

Name	Link
🔨 Latest commit	cab0f40
🔍 Latest deploy log	https://app.netlify.com/sites/v3-meteor-api-docs/deploys/662b5b30dfec1a0008a43512

[nachocodoner]

I'm wondering if we could develop tests to aid in this verification process. Could we add a self-test for this build stuff, perhaps even unit testing for this specific handling?

[netlify]

✅ Deploy Preview for v3-migration-docs canceled.

Name	Link
🔨 Latest commit	cab0f40
🔍 Latest deploy log	https://app.netlify.com/sites/v3-migration-docs/deploys/662b5b30d16000000760aca6

[zodern]

I tested this with the cause for the error from #13111, and this PR incorrectly allows the inconsistent constraints.

If you add this to Package.onUse:

  api.use('montiapm:[email protected]||3.0.0-beta.4');
  api.imply('montiapm:[email protected]');

Meteor should error since having different constraints for a package in api.use and api.imply is unsupported. When running with this PR, Meteor instead builds the package without erroring.

---

#13111 only updates one place that calls getDependencyMetadata. There's a second place in publishPackage that could also be updated to show better error messages. That might help with debugging this issue.