DPL-966 Replace yarn with npm as yarn is no longer required and is causing installation problems

[Sangeetha-Bheeman]

Describe the Housekeeping
As developers we should be able to install dependencies without any local installation problems and to keep it in line with other applications.

Who are the primary contacts for this story
Steve, Sangeetha

Who is the nominated tester for UAT
PSD

Acceptance criteria
To be considered successful the solution must allow.

• To install dependencies locally without causing any errors/problems to developers.
• The application to continue to work as expected with no loss of service for users.

[Sangeetha-Bheeman]

Tasks: To replace yarn with npm,

• Remove yarn.lock file
• Remove yarn commands from .gitignore and .prettierignore
• Replace yarn commands with npm in package.json for running scripts, if applicable.
• Replace yarn build with npm run build in compile-build.sh
• Change README.md, replace with the appropriate npm commands
  • To install dependencies(and to ignore old version dependencies to avoid errors - https://stackoverflow.com/questions/66239691/what-does-npm-install-legacy-peer-deps-do-exactly-when-is-it-recommended-wh) usenpm install --include-dev --legacy-peer-deps
  • For compiles and hot reloads for development npm run serve
  • Compile and minified for production npm run build
  • For tests npm run test:unit and npm run test:e2e:all
  • For linting npm run lint and to fix errors npm run lint -- --fix
  • For prettier npm run pretty and to fix errors npx prettier --write .
• Replace yarn with npm commands in the files .github/workflows/js_test.yml, .github/workflows/automated_release_and_build.yml, .github/workflows/lint.yml and .github/workflows/manual_build.yml
• Run npm install
• Ensure all tests pass
• Ensure CI passed and creates a release build
• Deploy to UAT