* remove python3-netifaces dependency

* make sure there is a mac addr (should always be..)

* no reason to call AddressFamily()

pam.authenticate will still be gated based on details of
common-auth.

Ticket: NAS-121406

This reverts commit 2e30220ee65e577b00c3583b8e31b517536d4438.

* SQLAlchemy 1.4 compatibility

* Expand `__[POSTCOMPILE_encrypted_provider_1` into valid SQL syntax

SQLAlchemy includes a variant on a bound parameter known as `BindParameter.expanding`,
which is a “late evaluated” parameter that is rendered in an intermediary state when
a SQL construct is compiled, which is then further processed at statement execution
time when the actual known values are passed. “Expanding” parameters are used for
`ColumnOperators.in_()` expressions by default so that the SQL string can be safely
cached independently of the actual lists of values being passed to a particular
invocation of `ColumnOperators.in_()`.

We need to render the `IN` clause with real bound parameter symbols as we store these
statements in HA database journal and execute them in a lower-level connection that
does not support these SQLAlchemy substitutions.

* fix failover event logic on inital HA config

* explicitly start fenced on zpool creation

* move fenced tests after pool creation