Separate the requirements file for each testing process

[Rebits]

Related issue
#3292

Description

Currently, every testing process makes use of a common requirement file. This is not scalable and produces several errors when more dependencies are added. I suggest changing this structure and splitting the requirements file into different requirements files.
Due to this being a breaking change and multiple CI processes depending on it, I suggest to maintain a general requirements file that will include all dependencies.

Added

• Requirements directory
• Requirements for several testing process: checkfiles, common, integration, performance, reliability, scan, system, tools

Updated

• General requirements file
• Add 1.26.5 for urllib3
• Change requests version to >=2.23.0

---

Testing performed

Tester	Test path	Jenkins	Local	OS	Commit	Notes
@user (Developer)		⚫⚫⚫	⚫⚫⚫			Nothing to highlight
@user (Reviewer)		⚫⚫⚫	🚫 🚫 🚫			Nothing to highlight

[Rebits]

After a meeting with @jmv74211 we have agreed to research other alternatives to this issue. Also, we should create topics for:

• Research dependency handlers
• Research the use of currently required dependencies
• Documentation of the use of the modules in the project

For now, this PR will be closed.