Construct version pinned

[syssi]

This is part of #13511. The construct version must be pinned because of an unstable API. The relaxed requirement of the eddystone_temperature sensor (beacontools) overrules the strict requirement of python-miio. All components are construct==2.9.41 compatible.

[MartinHjelmare]

It's good to link to a source describing the API changes and background to instability. Perhaps here:
http://construct.readthedocs.io/en/latest/transition29.html

[pvizeli]

I don't think that is needed. You have pinned this on your library and beacontools use: 'construct>=2.8.16,<2.10. In this case it should be correct done with docker. @balloob do we now also pin library they we are not based directly?

[syssi]

@pvizeli The latest docker images are build with construct 2.9.40 although python-miio 0.3.8 requires/pinned 2.9.31. This PR tries to avoid the problem as long it's not solved. If you rebuild the docker image (without pinning construct) the most recent version will be picked.

[balloob]

I'm fine with the pinning while we figure out why the Docker builds don't respect the range as defined by python-miio