Alarm Control Panel: Refuse to arm home or away if at least one zone is faulted

**Describe the problem you have/What new integration you would like**

Add a configuration option to prevent the alarm panel from being armed if there is at least one sensor showing a fault.
The option would not allow an alarm away arm to happen if any of the sensors are faulted. For arm home, the option would only prevent arming for those sensors without a bypass_armed_home key set for the zone.

**Please describe your use case for this integration and alternatives you've tried:**

The way it works currently is that it is possible to arm the alarm with a faulted zone. This causes the alarm to go into pending mode, then trigger the alarm. If a user walks or drives away after doing this, the alarm will go off. The user gets confirmation that the alarm is armed, but may not be aware that a zone is faulted.

My current workaround is to add 2 separate lists of tests as lambdas in the YAML code to test each group of arm home and arm away sensors, and provide ready/not ready binary sensors for use by homeassistant cards. This additional logic does not completely solve the problem though, as these binary sensors only provide status information, and do not prevent the user from arming the system in a faulted state.

Not having the system arm in a faulted state for arm away and arm home is the use case. It will prevent someone from arming the system, leaving the premises, and then have to return due to an alarm caused by the faulted zone.

**Additional context**

No implementation files or tests are identified. Start by locating the alarm control panel handling for arm-home and arm-away requests, then trace how faulted zones and the bypass_armed_home setting are evaluated. Done means a configuration option prevents away arming for any faulted zone and home arming for faulted zones without that bypass setting.

Written by the indexing model from the issue text.