Create a standard ruleset for New Relic One Catalog projects

[tangollama]

See this link for details: https://opensource.newrelic.com/oss-category/#new-relic-one-catalog-project

• [ ] valid LICENSE
• [ ] valid reference to Security policy in the README (look for # Security)
• [ ] contains THIRD_PARTY_NOTICES.md
• [ ] README contains New Relic One Catalog header
• [ ] README contains a reference to a thread on discuss.newrelic.com
• [ ] contains catalog directory with
  • [ ] config.json
  • [ ] screenshots directory
  • [ ] documentation.md
• [ ] contains a .github directory with workflows
• [ ] package.json contains a eslint and eslint-fix command

Follow up questions:

• Can we validate docs are present in the repo or should we check for a reference in the README?

cc: @melissaklein24 @jbeveland27

[jbeveland27]

@tangollama If this is specific to Catalog projects, should this ruleset contain all of the checks validate-nerdpack-action does? The validate action will run when PR'ing into the Catalog, but this could establish all of those files/commands being present before we get to that point (or we could just run validate-nerdpack-action in the Nerdpack repos 🤷 ).

Mainly wondering, do we want this action and ruleset to supersede the validate-nerdpack-action?

[tangollama]

More than anything, this is a PoC for the repolinter-action. Totally agree that these rules need to encompass the validate-nerdpack-action. I'll review and (try) to reconcile accordingly.

[prototypicalpro]

Here is my first draft of the NR1 config: https://github.com/aperture-science-incorporated/.github/blob/7a363c948c7f4293d559d92ae908f763a3ad3148/repolinter-newrelic-nr1catalog.json. An example issue this configuration generates is here: https://github.com/aperture-science-incorporated/cores/issues/19.