Dep-check: support for devOnly in meta capabilities

[AlekhyaYalla]

Currently, dep-check will enforce capabilities with devOnly key in devDependencies section only. It would be good to have a similar feature for meta-capabilities as well so that all the capabilities part of that meta-capability would be enforced under devDependencies only.

Eg:

 "react-redux": {
    name: "react-redux",
    version: "^7.2.8",
  },
  "ts-node": {
    name: "ts-node",
    version: "^10.7.0",
    devOnly: true
  },
  "meta/common": {
    name: "#meta",
    capabilities: [
      "react-redux",
      "ts-node"
    ],
    devOnly: true
  }

currently with the above profile, when meta/common is used in package.json->rnx-kit->capabilities field, then ts-node will be in devDependencies and react-redux will be in devDependencies + peerDependencies section.

Ask is for, with the above profile, both ts-node and react-redux will be added under the devDependencies section only.

Thanks!

[tido64]

I think we can do this, but it won't be done until #1890 is done. And it will most likely only be available in 2.x.