Add comments to requirements.txt to explain each package

[shivaahir158]

Motivate of the pull request

• To address an existing issue. If so, please provide a link to the issue:
• Breaking new feature. If so, please describe details in the description part.

Describe the technical details -

Adding comments next to each package in the requirements.txt file.
The comments give a short explanation of what each package does.
This makes it easier for developers to understand why each package is included.

Which part of the code base require a change

• Frontend:
• Backend:
• Library: <Specify the library name, e.g. npm packages>
• Plug-in: <Specify the plugin name, e.g. Webpack, jtest>
• Documentation
• Regression tests
• Continuous Integration (CI) scripts: requirements.txt

Impact of the pull request

• Require a change on Quality of Results (QoR)
• Break backward-compatibility. If so, please list who may be influenced.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.46%. Comparing base (6e6cdd8) to head (6350cd8).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #242   +/-   ##
=======================================
  Coverage   69.46%   69.46%           
=======================================
  Files         110      110           
  Lines        8607     8607           
=======================================
  Hits         5979     5979           
  Misses       2628     2628           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ravikiranchollangi]

Requirements.txt are usually auto-generated (at some point in future we will get to it).
The packages will be defined at their artifact hosting pages.