Repo Gardening: change the order of the tasks running

[jeherve]

Proposed changes:

We currently have 2 different tasks that can trigger Slack Notifications:

• triageIssues
• updateBoard

Both of those tasks rely on the notifyImportantIssues utility function to post to Slack. That utility, after posting a message to Slack, adds a label ("[Status] Priority Review Triggered") to ensure that we do not post to Slack multiple times.

As a result, the 2 tasks above cannot both post to Slack: the one that runs first does, and the other one bails because the label already exists.

I think the updateBoard task should take prriority, since it warns the team working on the product directly, while the triageIssues task "only" warns triage teams that will in turn contact the product teams if necessary.

As a result, I'd like the Board update task to run first, before issues get triaged, so that the Slack notifications potentially triggered by the board update task happen first, before the Slack notifications sent by the triageIssues task.

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

• N/A

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

• No

Testing instructions:

This cannot be tested in this repo before the PR is merged. It can only be tested in a fork.

[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.
  
• ✅ 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 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 reviewed, it can then be merged.
If you need an extra review from someone familiar with the codebase, you can update the labels from "[Status] Needs Team Review" to "[Status] Needs Review", and in that case Jetpack Approvers will do a final review of your PR.

[monsieur-z]

Looks straightforward enough 👍