chore(deps): update dependency inquirer to v9.3.8

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
inquirer (source)	9.2.12 -> 9.3.8

---

Release Notes

SBoudrias/Inquirer.js (inquirer)

v9.3.8

Compare Source

v9.3.7

Compare Source

v9.3.6

Compare Source

v9.3.5

Compare Source

• Fix issue with plugins relying on internal inquirer packages file structure.

v9.3.4

Compare Source

v9.3.3

Compare Source

v9.3.2

Compare Source

v9.3.1

Compare Source

• Fix risk of prototype injection.

v9.3.0

Compare Source

• Replace chalk with picolors (in 9.3.2 went to yoctocolors to stay with Sindre's packages and reduce amount of provenance.)
• Drop many dependencies in favour of native functions when possible.

No impact expected, but it's a large changes in dependencies. Let us know if you run into any issues upgrading!

v9.2.23

Compare Source

v9.2.22

Compare Source

• editor prompt: Fixed compatibility issue between default and waitUserInput options. #​1405

v9.2.21

Compare Source

v9.2.20

Compare Source

v9.2.19

Compare Source

v9.2.18

Compare Source

• On windows, we will now use unicode characters whenever possible

v9.2.17

Compare Source

v9.2.16

Compare Source

v9.2.15

Compare Source

v9.2.14

Compare Source

v9.2.13

Compare Source

---

Configuration

📅 Schedule: Branch creation - "after 5pm every weekday,before 3am every weekday,every weekend" in timezone Europe/London, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Oops! Looks like you forgot to update the changelog. When updating CHANGELOG.md, please consider the following:

• Changelog is read by country implementors who might not always be familiar with all technical details of OpenCRVS. Keep language high-level, user friendly and avoid technical references to internals.
• Answer "What's new?", "Why was the change made?" and "Why should I care?" for each change.
• If it's a breaking change, include a migration guide answering "What do I need to do to upgrade?".