Github recently added a new subdomain release-assets to their githubusercontent.com creating an issue when validating the incoming requests.

15.79 │ │        │                                                                 │ │
15.79 │ │        query='sp=r&sv=2018-11-09&sr=b&spr=https&se=2025-06-12T20%3A29%3… │ │
15.79 │ │        │   fragment=''                                                   │ │
15.79 │ │        )                                                                 │ │
15.79 │ │ self = <github.Requester.Requester object at 0xffffaed27bc0>             │ │
15.79 │ │  url = 'https://release-assets.githubusercontent.com/github-production-… │ │
15.79 │ ╰──────────────────────────────────────────────────────────────────────────╯ │
15.79 ╰──────────────────────────────────────────────────────────────────────────────╯
15.79 AssertionError: release-assets.githubusercontent.com
------

This PR updates the validation on the domain name instead of the full subdomain.domain

Message from github:

Thank you for reaching out to GitHub Support!
I checked in with our engineering teams about this.
That’s correct, we have recently turned on a feature flag that adds the address release-assets.githubusercontent.com for release assets.
This change comes a part of some internal service updates and is planned to be permanent.
The *.githubusercontent.com address is listed as a wildcard in the GitHub META API Endpoint and depending on the activity performed you may see connections to many different githubusercontent.com subdomains, with some of them being new from time to time.

Fixes #3315.