Prevent installation of incompatible Apify SDK versions after breaking releases

[janbuchar]

Last time this happened was after the 0.6 release - in projects that use the SDK, crawlee was updated to 0.6 and the dependency resolver installed an old SDK version (2.0.x) that is incompatible, but doesn't have an upper version constraint for crawlee.

We have a few options:

• ignore this and try to release a new SDK right after crawlee each time
• unpublish the old SDK (might break for users who are locked to that version)
• release a patch version of the SDK with correct dependency specs + the previous item
• release a patch version of the SDK that checks crawlee version on runtime
• check SDK version in crawlee on runtime

Not sure which of the repositories this belongs to, so I just chose one...