required-review: Add consume option

[anomiex]

Proposed changes:

In the monorepo we have a bunch of projects owned by different teams. Everyone should be able to update lock files and changelog entries, which means that the rules for each team's projects has to exclude those files so only the "anyone can update these files" rule applies.

This adds a new rule option, consume. When set on a rule, any paths matching the rule will be ignored for all later rules in the file. This will allow us to not have to repeat these exclusions everywhere.

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

None. Has been on my list for a long time, and the most recent update made me decide to finally do it.

Does this pull request change what data or activity we track or use?

No

Testing instructions:

• Use the test.sh script to run against various PRs, I guess.
  • Probably would be good to test in combination with Update required-review config #29318 that adjusts the monorepo config to use the new option.
• Check added docs for typos and sense.

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ All commits were linted before commit.
  
• ✅ Add a "[Status]" label (In Progress, Needs Team Review, ...).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Once your PR is ready for review, check one last time that all required checks (other than "Required review") appearing at the bottom of this PR are passing or skipped.
Then, add the "[Status] Needs Team review" label and ask someone from your team review the code.
Once you’ve done so, switch to the "[Status] Needs Review" label; someone from Jetpack Crew will then review this PR and merge it to be included in the next Jetpack release.

[jeherve]

It does make sense. I wasn't super sure of the consume name at first, but I cannot come up with anything better, so that's alright I suppose :)

[anomiex]

The only other thing I could come up with was "consumePaths" if we want to be a little clearer about what's being consumed.

[jeherve]

I'm not considering this a blocker; we can always blame things back to this PR whenever doubts will come up.