Fix python module versions within requirements.txt

[cmonr]

Description

After finding and solving an issue with colorama being updated (resolved with #8390), @studavekar brought up a good comment that we should do the same with other packages.

Requirements.txt should be fixed to specific versions, and have a process to update versions on a regular bases. This issue is for the first part of the problem, with @ARMmbed/mbed-os-test already working on the second.

Issue request type

[ ] Question
[x] Enhancement
[ ] Bug

[OPpuolitaival]

I think that this make things a lot easier because now it is not easy to track when tools versions are updated. When there are specific version then PR itself is used to test the new version of the tool

[cmonr]

Aaand it looks like we just got hit again by not having versions fixed/pinned.

Last working master build: https://travis-ci.org/ARMmbed/mbed-os/builds/442254105
The next build after: https://travis-ci.org/ARMmbed/mbed-os/builds/442300780

(urllib3 was updated from 1.23 to 1.24)

[ciarmcom]

Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-30

[yennster]

@cmonr Does #8446 fix this issue?

[studavekar]

@yennster this issue is to review https://github.com/ARMmbed/mbed-os/blob/master/requirements.txt and update to latest working version. As of now, most of packages say >= which are causing failures as latest version of module may not be compatible with other modules used.

problem seen

1. htrun fails with mbedgt: cannot import name MbedBoard htrun#222
2. Pin urllib3 pip module in requirements.txt #8446

[cmonr]

@yennster Not completely.

#8466 was the immediate fix needed to make master green again, but this ticket is a placeholder to make sure that we update requirements.txt so that all module versions are updated accordingly.

Feel free to assign the internal ticket to me.

[yennster]

@cmonr Moved to IOTCORE and assigned it to you (IOTCORE-571)