Not typing indicators, etc.

Notify only once per day (using expiring redis key).
Can notify MUC or user, always sends directed presence first so it will join MUC
if not joined.
Ignore all messages direct to the component, mostly to throw out live messages
from MUC if we join that to notify.

Just gives them the information and we're done. Support has to manually process
these payments anyway.

To show mailing address, eTransfer address, Bitcoin addresses, and allow
generating a new Bitcoin address.

An invalid customer id is an error from braintree, so handle the error and
return an empty list of payment methods.

Also rename buy credit to top up

And use that in registration instead of implementing it inline

So say feature-not-implemented if we haven't got it with some other handler.

* conditionally-show-commands:
  Only show buy credit option if customer has a plan and a credit card
  Show commands conditionally (plus add voicemail record command)

Refactor to a factory that allows commands to be shown conditionally, so that
the voicemail record command can only be shown if the customer has a forwarding
target set up.

* credit-card-bonus:
  Insert bonus when paying by credit card

* tel-search-temp:
  No tel picker yet, so just go to the webpage

Otherwise we go in hierarchy order and stanza comes last.

* passthrough-commands:
  Pass through commands we know the SGX can handle
  Pass everything from SGX to user, not just <message/>
  Remove some of the noise from the command list

* bitcoin-tmp:
  Save legacy session for Bitcoin flow

Typo not caught by tests because this method had none.  Add a test, fix the typo.

These lines won't work because not processing an iq or anything with a node
here.  Set up sentry in a sensible way for messages.

This is not a permanent solution, but for now it will allow Bitcoin flow users
to get the same message from the cronjob that legacy web flow users get, and
thus complete their signup using the legacy web flow.

Eventually we'll want to reverse this and direct every Bitcoin activation via a
new end flow.

Direct users to the homepage if they haven't selected a tel yet.  Not what we
want eventually, but better than crashing.

* create-reset-sip-account:
  Create or reset SIP account
  Factor out Catapult connection

New command to create or reset SIP account.  Always try create first because
it's faster and more common, fall back to search the list for our account if
that fails due to conflict.  Password is always randomly generated from the
mnemonicode word list.

So that every object which needs to talk to Catapult does not need to know
everthing about it.

Customer has a CustomerUsage which can fetch data to build a UsageReport
which returns a jabber:x:data form "table" as per spec for per-day in
the last month.

Minutes come from cdr table in postgresql.
Messages come from redis.

Capture in #panic and a few other places, add customer and route context
as well as some initial breadcrumbs in the register command.

To allow these modules to be used in isolation (especially when
testing).

add_to_form no longer needs a promise or a network call, instead we use
a factory to get that data up front and inject the dependency.

New BuyAccountCreditForm#parse to get the relevant data back out of an
XMPP form.

Some changes to Transaction and sgx_jmp.rb to use the new method
semantics.

* count-outbound-messages:
  Store customer outbound messages/day for 1 year in redis

Storage is a sorted set, with dates as the values and message counts as the
scores.  Use zincrby to increment the message count by 1 on each new message.
Use zremrangebylex to remove all items older than 1 year so the set does not
grow unboundedly.

Dates with known message counts can be found using zrangebylex. Scores can be
had one at a time with zscore.  In redis 6.2+ zrange bylex withscores or zmscore
may also be used, but that is only in Debian experimental at time of writing.