chore(react-router): migrate to eslint, add prettier

[liamdebeasi]

Pull request checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
  • Some docs updates need to be made in the ionic-docs repo, in a separate PR. See the contributing guide for details.
• Build (npm run build) was run locally and any changes were pushed
• Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

@ionic/react-router has peer dependency issues when using tslint and tslint-ionic-rules. This requires the use of --legacy-peer-deps when releasing the package.

What is the new behavior?

• Migrates @ionic/react-router from TSLint to ESLint and uses the Ionic ESLint config: https://github.com/ionic-team/eslint-config
• Updates Prettier to the latest version and installs the Ionic Prettier config: https://github.com/ionic-team/prettier-config/
• Updates the CI scripts to avoid the --legacy-peer-deps flag and prefer npm ci instead of npm install

Note: For ESLint I only used rules that likely would not cause any functional changes. We've been burned before with rules such as prefer-optional-chain causing functional changes. I also added several ignores to quirks in Ionic React such as how we use the spread operator to remove keys from the remaining object (but then never use the keys)

Does this introduce a breaking change?

• Yes
• No

Other information

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[liamdebeasi]

These were duplicate commands that I removed