Search: allow the Search team to approve changes to the package

[jeherve]

Changes proposed in this Pull Request:

• The Search package is the work of the Search team. They're familiar with its structure and codebase, they should be able to approve changes just like Jetpack Approvers currently can.

Jetpack product discussion

• N/A

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

• No

Testing instructions:

• Not much to test in this PR.

[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.

---

Search plugin:

• Next scheduled release: February 1, 2022.
• Scheduled code freeze: January 24, 2022.

[anomiex]

This won't work as written since the "Jetpack and packages" block will still require a Crew review. See on #22461 #22473 we have it looking for a reviewer at both here and here

Adding a pattern '!projects/packages/search/**' in there (around line 24-ish) to exclude the search package from that block should fix it.

[jeherve]

thanks for catching that! Pushed your suggestion in 78bd530

[anomiex]

Looks good, but one (optional) suggestion inline