Minor update to Frontend Readme

[Jooms]

Updating this to the new format that the backend/README.md uses

Resolves #51

[hardikpatil]

Looks good to me!

[decoles]

LGTM

[sathyanarayanan-v]

Can we have npm ci instead of npm install to make sure we don't update packages accidentally?

[Jooms]

npm ci

From: https://docs.npmjs.com/cli/v9/commands/npm-ci

Is only meant to be used in things like CI, testing, etc. Meant to be a clean install of dependencies. From my understanding npm install is the correct command to use for development.

I do understand what you're calling out though. npm install will pull the latest minor / patch versions for each dependency in the package.json file, which can (and likely will) cause the package-lock.json file to change every time. I assume there is an industry / common way of handling this in full-fledged JS teams, but it seems that npm-ci isn't it (at least with the documentation I see).

There's definitely room for discussion on "How do we improve the rampant merge conflicts we run into with package-lock.json". Especially when documentation shows that 1) we're supposed to keep package-lock.json committed, and 2) npm install is supposed to be used for development environments.

Package-lock.json docs: https://docs.npmjs.com/cli/v8/configuring-npm/package-lock-json

This file is intended to be committed into source repositories, and serves various purposes ...

Please create a Discussion on this topic if you'd like to discuss it more.