Support binding IPv4 AND IPv6 instead of just either one or the other

[Omar007]

At the moment the configuration is limiting input to either an IPv4 address or an IPv6 address even though the underlying waitress server has no problem binding both at the same time.
This updates the configuration to pass the wildcard value on to the waitress server so Bazarr can serve in both single and dual stack environments ootb.

[morpheus65535]

Thanks for your contribution and sorry for the delay.

[morpheus65535]

@Omar007 can you take a look at my review and comments?

[Omar007]

@morpheus65535 which ones where? I don't see any 🤔

[morpheus65535]

@morpheus65535 which ones where? I don't see any 🤔

Sorry I forgot to submit them 🤦‍♂️

[morpheus65535]

Thanks!

[JaiZed]

There is a typo in logger.py at line 65:
if record.level != loggin.ERROR:

The name logging is misspelled as loggin without the letter g.

Was this part of the code tested?
How did this pass through the automated checks?!

Also, what happens if we get a CRITICAL log message?
It looks like it will be filtered out if the line above is corrected.
Is that desired?

[Omar007]

Was this part of the code tested?

It was locally but looks like this somehow slipped between the commits/push. I have it correct locally so I think I just didn't commit it properly, that's my bad 🙇

How did this pass through the automated checks?!

This I have no idea for. The initial mistake is def. on me but I do feel like it should've been caught by something; as far as I can tell there is a workflow present that runs the application 🤔

Also, what happens if we get a CRITICAL log message?
It looks like it will be filtered out if the line above is corrected.
Is that desired?

I'd say that is not desired. I've pushed a new MR to deal with the logging fallout of this one; #2663. Please take a look at that.