Update mbed-cloud-sdk in requirements.txt

[cmonr]

Description

Fixes #8143

Pull request type

[x] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Breaking change

[cmonr]

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 3088
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/8160/

Triggering tests

/morph test
/morph export-build
/morph mbed2-build

[mbed-ci]

Test : SUCCESS

Build number : 2876
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/8160/2876

[mbed-ci]

Exporter Build : SUCCESS

Build number : 2698
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/8160/

[0xc0170]

I still do not understand why we are so strict (==) instead of >= which would actually also fix this. any upcoming patch will require this update, not ideal?

To take any upcoming patch and minor but not major would as a fix?

[cmonr]

@0xc0170 I was following the style that was there before.

I'm actually of the opinion that ALL requirements should be pinned against specific versions, only updating version numbers once they're tested and in CI.

[cmonr]

@MarceloSalazar @teetak01 Any preference one way or another?

[MarceloSalazar]

My preference is to have fixed versions, so we can guarantee reproducibility by anyone.
Loose dependencies mean we don't have control.

[0xc0170]

Loose dependencies mean we don't have control.

Depends on how loose we choose. Updating to a patch release should be safe anytime. having strong version match as in here will result in updating it often. As it was before ==, I won't challenge it here but will take this to a new issue.