Honor EncodingType in response with ListObjectsV2 as with ListObjects

[nanawel]

There seems to be a bug with ListObjectsV2 when dealing with type encoding in responses. The special middleware that's responsible for url-decoding the values in some nodes can only be triggered with ListObjects, so in V2 the client ends up with URL-encoded strings that are not valid in the rest of the application.

aws-sdk-php/src/S3/S3Client.php

Lines 642 to 652 in 0de11ad

	private function getEncodingTypeMiddleware()
	{
	return static function (callable $handler) {
	return function (Command $command, $request = null) use ($handler) {
	$autoSet = false;
	if ($command->getName() === 'ListObjects'
	&& empty($command['EncodingType'])
	) {
	$command['EncodingType'] = 'url';
	$autoSet = true;
	}

This patch should fix this issue while keeping compatibility with PHP 7.

[stobrien89]

Apologies for the very delayed response. Just a minor change and test requested

[stobrien89]

Can we change this to a str_starts_with()?

[stobrien89]

Could you either turn this test into a parameterized test which call both listObjects and listObjectsV2 or create a separate unit test for listObjectsV2?