requests: Use the Any trick in HTTPError

[Akuli]

See #10875 for context.

Usually, when you get a HTTPError, the response will be set. Specifically, it will always be set when the requests library raises the error.

But people also use HTTPError as a generic "just show this generic error message" exception that doesn't include any details about what happened. For example, paasta_tools/mesos_maintenance.py has plenty of code like this (as pointed out by mypy_primer):

    try:
        status = get_maintenance_status(mesos_config_path).json()
        status = status["get_maintenance_status"]["status"]
    except HTTPError:
        raise HTTPError("Error getting maintenance status.")

I think we should get the best of both worlds with the Any trick.

[Akuli]

The mypy_primer output isn't really comparable to the previous PR, because people have already added redundant casts and None checks:

• typing updates python-poetry/poetry#8541
• schemathesis/schemathesis@b231ab6
• internetarchive/openlibrary@5dc2dd1
• Allow for an HttpError without a response pypa/twine#1023

Also, mypy doesn't warn about unnecessary checks or casts: an if statement with Response | Any or a cast from Response | Any to Response could be useful.

[github-actions]

Diff from mypy_primer, showing the effect of this PR on open source code:

cloud-init (https://github.com/canonical/cloud-init)
- cloudinit/url_helper.py:343: error: Item "None" of "Response | None" has no attribute "status_code"  [union-attr]
- cloudinit/url_helper.py:344: error: Item "None" of "Response | None" has no attribute "headers"  [union-attr]