BlueZ or_patterns are not type checked

[dlech]

• bleak version: 0.20.0a1
• Python version: 3.10
• Operating System: Linux
• BlueZ version (bluetoothctl -v) in case of Linux: 5.63

Description

When using passive scanning, or_patters are currently required for the BlueZ backend because that seems the only way to get BlueZ to do passive scanning. When we do this, we register a new D-Bus object and the or_patterns are read as a D-Bus property. If we get the types wrong, dbus-fast logs an error, but there is no way to raise an exception since it is happening in a background task.

With #1146, we can get a callback that there was a problem, but no way to tell what the problem is. So it would be better if we did a type check during __init__ of the BleakScanner instead to get an early failure and a more helpful error message.