Normalize Azure DevOps PR status failures into GitHostingException

[Copilot]

Azure DevOps pull request status is parsed from an open-ended wire string; unknown values were escaping as NotSupportedException, breaking the provider contract that hosting failures surface via GitHostingException. This change routes unrecognized status values through GitHostingRequestException with provider/HTTP/body context.

• Behavioral fix

  • AzureDevOpsProvider now maps unknown PR status values to GitHostingRequestException instead of throwing NotSupportedException.
  • Exception includes Name, HttpStatusCode, and raw response body to preserve diagnostics for malformed/preview/future status values.

• Mapping path update

  • PR mapping now passes response context (statusCode, responseBody) into status conversion so failures are translated in the hosting-exception hierarchy at the point of conversion.

• Focused coverage

  • Added a targeted test asserting an unrecognized status (e.g. "notSet") from pull request listing throws GitHostingRequestException and carries the response context.

private GitPullRequestState ToGitPullRequestState(string? status, HttpStatusCode statusCode, string responseBody) => status switch
{
	"active" => GitPullRequestState.Open,
	"completed" => GitPullRequestState.Merged,
	"abandoned" => GitPullRequestState.Closed,
	_ => throw new GitHostingRequestException(
		$"Azure DevOps reported an unrecognised pull request status '{status}'.",
		Name,
		statusCode,
		responseBody),
};

• Fixes AzureDevOpsProvider throws NotSupportedException instead of GitHostingException for an unrecognized pull request status #106

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud