Add feature to handle the range request properly by adding logic to process the range request

[DanielPickens]

Description:
Add a new feature method to handle range requests from streaming a TS serving_request that fixes out of range request property objects when making a call when serving_request.protocol >= (1, 1): tries to get
r = httputil request range. This would add extended functionality for handling of range requests in bytes in self._stream_url(serving_request, kwargs.get("url")) object to handle range of served_requests kwargs object property calls to
get requests that need to handle [Content- Request] and [Accepted Request} range property by assessing if start, end = r[0]
cherrypy.response.headers['Content-Range'] = f'bytes {start}-{end}/{sys.maxsize}'
cherrypy.response.headers['Accept-Ranges'] = 'bytes'
has handled the request range properly for bytes in content range calls to the cherrypy.response property object that handles header requests for for bytes in self._stream_url range loop check on streaming bytes in content range more properly.

Why is this needed:
This would fix the issue of the range loop not handling the range request properly by adding a logic to process the range request such as:

      if r:
                start, end = r[0]
                cherrypy.response.headers['Content-Range'] = f'bytes {start}-{end}/{sys.maxsize}'
                cherrypy.response.headers['Accept-Ranges'] = 'bytes'
                cherrypy.response.status = 206

What would you like to be added:
A new feature that handles the range request properly by adding logic to process the range request that would increase response header security and decrease overhead, as well as speed up the API calls to server_request_headers for start and ending response API headers requests.

Who is this feature for?
@hulu/dripls/main.py