Marks brittle specs with pending

The Account model specs are easily broken by doing radical things like
adding a second, unrelated spec.

The client based logic but not having the ability to switch them with
independent caches and working VCR recording is hold up other
development when they appear to be working.
Isolate another spec's config file

Sharing configs across tests suffers from another shared state problem
where the config incorporates access/refresh token caching so an access
token is cached with sanitised values "<TOKEN>" and used to replay and
failing.

Seems the only safe way to test this code is to drop every spec inside a
temporary dir for caching.
Adds Firewall policy subcommand

Can now update a firewall policy's name or description

Tests to confirm the update has occured (by making independent API calls)
fail out of sequence due to global config and token caching. They may or
may not work depending on which specs have run before so are pending.

The specs are triggering an issue in account specs as well.