Support patterned and default HTTP status codes

[dbanty]

Closes #1271 and #832

[Copilot]

Pull Request Overview

This PR implements support for patterned and default HTTP status codes in OpenAPI specifications, enabling the use of status code patterns like 2XX, 4XX, and default in addition to specific status codes like 200.

• Introduces new HTTPStatusPattern class to handle parsing and validation of status code patterns
• Refactors response handling to support both specific codes and ranges with proper precedence ordering
• Updates template generation to handle default responses and status code ranges in generated client code

Reviewed Changes

Copilot reviewed 72 out of 72 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
openapi_python_client/parser/responses.py	Adds HTTPStatusPattern class and Responses container with pattern/default separation
openapi_python_client/parser/openapi.py	Updates Endpoint class to use new response structure and pattern parsing
openapi_python_client/templates/endpoint_module.py.jinja	Modifies template to generate range checks and handle default responses
tests/test_parser/test_responses.py	Updates tests to use HTTPStatusPattern instead of HTTPStatus
end_to_end_tests/	Adds new test endpoints and updates generated client files for pattern support

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[dbanty]

Just gotta add tests for coverage

[Copilot]

Pull Request Overview

This PR adds support for HTTP status code patterns (2XX, 4XX, etc.) and the special default status code in OpenAPI specifications. This closes issues #1271 and #832.

• Replaces the simple integer status code handling with a new HTTPStatusPattern class that can parse patterns like "2XX" and "default"
• Refactors endpoint responses to use a new Responses container that separates patterned responses from default responses
• Updates template generation to handle status code ranges and proper precedence ordering (specific codes first, then patterns, then default)

Reviewed Changes

Copilot reviewed 72 out of 72 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
openapi_python_client/parser/responses.py	Core implementation of HTTPStatusPattern class and Responses container for handling status code patterns
openapi_python_client/parser/openapi.py	Updated endpoint parsing to use new status pattern system and response organization
openapi_python_client/templates/endpoint_module.py.jinja	Modified response parsing template to handle status code ranges and default responses
tests/test_parser/test_responses.py	Updated tests to use new HTTPStatusPattern objects instead of integer status codes
Multiple generated API files	Generated code showing proper handling of status code patterns with range checks and blank lines

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

The parse_response macro is imported twice in the same import statement, which is redundant and could cause confusion.

Suggested change

	arguments, client, kwargs, parse_response, docstring, body_to_kwarg, parse_response %}
	arguments, client, kwargs, parse_response, docstring, body_to_kwarg %}

[obs-gh-peterkolloch]

Thank you, @dbanty! I upgraded to 0.26.0 and it did not result in code generation differences relative to my pull request.

Yours is definitely an improvement! Thanks.