chore: picomatch 2.3.1 high vulnerability fix (#700)

[liming-cheung-nhs]

Description

Cherry picked off main: Dependabot vulnerability issue.
Merged under #700

Context

Type of changes

• Refactoring (non-breaking change)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would change existing functionality)
• Bug fix (non-breaking change which fixes an issue)

Checklist

• I am familiar with the contributing guidelines
• I have followed the code style of the project
• I have added tests to cover my changes
• I have updated the documentation accordingly
• This PR is a result of pair or mob programming

---

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

• I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

[liming-cheung-nhs]

Noted a cherry pick did not pull over the package-lock.json.
On checking release 2 branch

• with npm audit - no picomatch vulnerability seen.
• npm ls picomatch - can see vulnerable picomatch 2.3.1 is not used

This PR is not requlred on release 2 branch.