[tests-only] Fix Guzzle7 exception handling in HttpRequestHelper

[phil-davis]

Description

The getResponse() method was removed from GuzzleHttp\Exception\ConnectException in Guzzle7.

It still exists in GuzzleHttp\Exception\RequestException

So not all exceptions have a getResponse() method. Be more careful to only try to process a RequestException and check for a response. Do not catch other exceptions. They will throw higher up and eventually Behat will catch them and fail the test scenario and report the exception.

Related Issue

• Fixes [Test-Framework] HttpREquestHelper not compatible with Guzzle 7 #39250

How Has This Been Tested?

CI - although the exception handling only happens in unusual circumstances.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Database schema changes (next release will require increase of minor version instead of patch)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:
• Changelog item, see TEMPLATE

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information