[FEAT] Make the use of `pipreqs` optional and ensure no duplicates or inconsistencies in the generated file

[Coopyrightdmin]

Problem Statement

Currently, the use of pipreqs is mandatory, which may overwrite pre-selected versions of packages. Moreover, there have been instances where the generated file contains duplicates or inconsistencies, leading to potential issues during container setup.

Benefits

Making pipreqs optional and ensuring a clean, consistent generated file would:

• Preserve user-specified package versions, allowing for more consistent and controlled environment setups.
• Minimize the risk of errors during container initialization due to problematic requirements files.
• Enhance user confidence in the tool, knowing that generated files will be free of duplicates and inconsistencies.

Additional context

For users who have specific package versions in mind, overwriting them using pipreqs can be problematic. Ensuring a clean and consistent output, without duplicates, is crucial for smooth and error-free container deployments.

Priority/Severity

• [x] High (This will bring a huge increase in performance/productivity/usability/legislative cover)
• [ ] Medium (This will bring a good increase in performance/productivity/usability)
• [ ] Low (anything else e.g., trivial, minor improvements)

[Coopyrightdmin]

I've added the --skip-pipreqs option to address the concern raised in this ticket. With this option, users can now opt out of the automatic use of pipreqs, thereby preserving user-specified package versions and minimizing risks associated with generating inconsistent or duplicate dependency files.