Adjust unit tests to account for the new connection timeout parameter

[plamut]

The google-cloud-core release v1.1.0 introduced a new optional timeout parameter to the JSONConnection object.

The timeout is passed down to the transport layer, which breaks several assertions in unit tests across different libraries, thus the assertions need to be adjusted.

Additionally, the version pins of the core dependencies need to be bumped in order to assure that core connections that support timeouts are always used.

Update:
Looking at #10094, security center, spanner, and storage fail for other reasons, thus their respective labels are not applied.