Bump simple-git to 3.3.0 to fix high severity issue

[mraible]

I saw our vulnerabilities badge has two issues listed on https://snyk.io/test/npm/generator-jhipster. This fixed the first one. Other updates:

 aws-sdk                      2.1087.0  →  2.1092.0
 axios                          0.26.0  →    0.26.1
 prettier-plugin-packagejson    2.2.15  →    2.2.16
 eslint                         8.10.0  →    8.11.0
 eslint-plugin-chai-friendly    ^0.7.1  →     0.7.2
 mocha                           9.2.1  →     9.2.2

I did not update chalk because chalk 5 is a breaking change.

After these changes, npm audit shows:

# npm audit report

ansi-regex  >2.1.1 <5.0.1
Severity: moderate
 Inefficient Regular Expression Complexity in chalk/ansi-regex - https://github.com/advisories/GHSA-93q8-gq69-wqmw
fix available via `npm audit fix --force`
Will install insight@0.8.4, which is a breaking change
node_modules/inquirer/node_modules/ansi-regex
node_modules/string-width/node_modules/ansi-regex
  strip-ansi  4.0.0 - 5.2.0
  Depends on vulnerable versions of ansi-regex
  node_modules/inquirer/node_modules/strip-ansi
  node_modules/string-width/node_modules/strip-ansi
    inquirer  3.2.0 - 7.0.4
    Depends on vulnerable versions of string-width
    Depends on vulnerable versions of strip-ansi
    node_modules/inquirer
      insight  >=0.9.0
      Depends on vulnerable versions of inquirer
      node_modules/insight
    string-width  2.1.0 - 4.1.0
    Depends on vulnerable versions of strip-ansi
    node_modules/string-width

5 moderate severity vulnerabilities

---

Please make sure the below checklist is followed for Pull Requests.

• All continuous integration tests are green
• Tests are added where necessary
• The JDL part is updated if necessary
• jhipster-online is updated if necessary
• Documentation is added/updated where necessary
• Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

When you are still working on the PR, consider converting it to Draft (below reviewers) and adding skip-ci label, you can still see CI build result at your branch.