fix: upgrade urllib version to fix vulnerability

[AleJo2995]

Types of changes

• Hot fix (emergency fix and release)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Documentation (change which affects the documentation site)
• Breaking change (fix or feature that would cause existing functionality to change)
• Release (develop -> main)

Quality assurance (all should be covered).

• My code follows the code style of this project.
• Documentation for my change is up to date?
• My PR meets testing requirements.
• All new and existing tests passed.
• All commits are signed-off.

Summary

Closes #1467

Key links:

• Sonar coverage

Before you merge

• Ensure it is a 'squash commit' if not a release.
• Ensure CI is currently passing
• Check sonar. If you are working for a fork a maintainer will reach out, if required.

[AleJo2995]

@vikas-agarwal76 , @mrgadgil I have done what documentation suggests by pinging urllib3 dependency to 1.26.17 to solve vuln issue stated here and tests are passing completely fine. Now, we need somehow to do some testing against that vulnerability per-sé, but the only way I see is to point any of the repos using trestle right now against this particular branch and run vul scan again. Is there any recommendation here that you can provide so it's not tied up only to that one?

[vikas-agarwal76]

LGTM. Please merge after testing.

[AleJo2995]

Done, tested out. Remediation will be addressed with the change