Visualize robot motion

[Raidakarim]

Describe this pull request. Link to relevant GitHub issues, if any.

This PR includes issue #22 deliverables as detailed in the following:

• Lock icon (svg image in react button) design and implementation for stopped/paused motion in the header implemented
• CircleProgressBar functional component implementation that contains circle progress bar with green color showing smooth progression, gray trail line, progress level percentage in text, circle formation in progress rate of robot motion
• Some readme comments for Ubuntu 22 and corresponding installation that will help with dummy nodes running in local
• Add motion time in moving screen above the progress bar
• Add text when user refreshes page in paused mode

TODO: the responsiveness problems of header (such as fitting all buttons/icons) will be addressed in the app responsiveness issue #9

Explain how this pull request was tested, including but not limited to the below checkmarks.

I tested the implementations by running the app screens in my local Ubuntu 22 chromium browser and ensuring:

• the lock icon appear in the header in robot's non-moving states and when the pause button is clicked
• the circle progress bar appears in robot's moving screens and when the robot is not paused
• the circle progress bar shows the correct progress level in its text and smoothly forms the circle at this rate, when run along with dummy nodes
• motion time appears in moving screens as expected
• refreshing page in different devices rendered text in paused mode

---

Before creating a pull request

• Format React code with npm run format
• [N/A] Format Python code by running python3 -m black . in the top-level of this repository
• Thoroughly test your code's functionality, including unintended uses.
• [N/A] Thoroughly test your code's responsiveness by rendering it on different devices, browsers, etc.
• Consider the user flow between states that this feature introduces, consider different situations that might occur for the user, and ensure that there is no way for the user to get stuck in a loop.

Before merging a pull request

• Squash all your commits into one (or Squash and Merge)

[amalnanavati]

Great work on this! The requested changes are quite small; once you have made them this should be ready to approve.

[amalnanavati]

See requested changes below.

[amalnanavati]

LGTM