Remove or reimplement 'warnings' from urifunctions.py et al.

The code that handled the warnings keyword in dqsegdb/urifunctions.py was removed from several functions in MR # 75. The keyword was added to the function definition for _auth_request() in urifunctions.py, because doing so prevented an error from urllib_request.urlopen() [1], but the variable does nothing. The code to do something with the contents of the variable should be reimplemented, if it's worth it, or the upstream code that passes along the variable (in numerous locations) should be removed.

[1] Slightly rambling and repetitive explanation: After a near-final version of MR # 75 was implemented, running the code produced the error TypeError: urlopen() got an unexpected keyword argument 'warnings'. This is because any keyword argument passed to getDataUrllib2 that didn't match a keyword argument in the function definition was collected in **urlopen_kw and passed on to _auth_request(), and from there to urllib_request.urlopen(). Before MR # 75, warnings did match a keyword argument in the definition of getDataUrllib2(), so it wasn't passed through **urlopen_kw, but after the MR, getDataUrllib2() does not include a warnings keyword, so warnings is included in **urlopen_kw, which is then passed to _auth_request() (as **urlopen_kw), which then collects all unmatched keyword arguments in **kwargs (which now includes warnings), which is then used to connect to the URL, using urllib_request.urlopen() (in with urllib_request.urlopen(request, **kwargs) as response:). But since urllib_request.urlopen() doesn't recognize the warnings keyword argument, it throws an exception.

Looking at dqsegdb/apicalls.py, warnings is used in a lot of places, most, but not all, of which are in functions that call urifunctions.getDataUrllib(); so getting rid of them in those function definitions will produce backwards-incompatible changes, in case anything else tries to use those functions with that parameter set; on the other hand, as it is now, documentation for each of those functions now says that it will do something with that parameter that it definitely does not do, e.g., from the dqsegdbCheckVersion() docstring:

    warnings : `bool`
        show warnings for `HTTPError` (as well as raising exception),
        default: `True`

In implementing MR # 75, I chose to leave the parameter there, maybe with a note in the function docstrings about it doing nothing right now, and leave the option for it to be reimplemented later, if someone wants to add the appropriate code, and I added it to the definition of _auth_request(), so that it isn't included in **kwargs and passed to urllib_request.urlopen(). warnings is not actually used in _auth_request() at this time.

At some convenient time in the future, someone should either implement some code to perform the documented uses of warnings or remove it entirely from all usage in this package.