Fixing breaking prod issues w/ client hardcoded IP and client dockerization

[EricLi-Dev]

Changes:

1. client/Dockerfile & docker-compose.yml

• We had issues dockerizing the frontend container in production as the service just hangs on npm install packages. I switched the Docker image to a more compatible version from this github issue.
• Also changed to build the frontend container on a linux platform

2. client/Api/UsersApi.jsx

• Whenever we changed the IP of the server (for a reboot or some other problems), the previous hardcoded IP would break login and signup functionality.
• Changed it to take the IP from a variable in .env

3. README.md

• Documented where to include .env and IP address for the above change to work.

4. client/components/profile.jsx

• Had a problem w/ npm run build with the escape character for "{username}'s profile". Small change to fix issue.

Demo:
After adding the IP in client/.env. Using Jubayer's example profile that currently lives in the production DB.

a) npm run build && npm run start - Starts the frontend on production so logins and signup hit the production DB

b) npm run build && npm run dev - Starts the frontend on development so logins and signup hit the local DB.

[George-Sucuzhanay]

the readme looks great and good catch on profile component bug

[Dulinag]

lgtm