* 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.

* wording:
  Update instructions to be closer to what is in current web signup

Allows us to advertise support address, for eventual inclusion in Cheogram adhoc
bot help output.

Keep this deprecation message in so that users with this still in roster know
where bot has moved.

* pass-messages:
  Pass messages to and from the SGX

* web-register-start:
  Hidden command to allow jmp-register to start a web registration

This is the command jmp-register will use to tell use a certain claimed JID
wants a certain tel.  We relay that to cheogram and save in web_register_manager
the tel associated with the JID cheogram assigns to the target.

Rewriting the from/to as appropriate.

* create_customer_id:
  Create customer_id if it does not exist before we start registration
  Break out CustomerPlan
  Inject BackendSgx per customer

We had Plan and Customer but the relationship between the two lived
entirely in Customer, which was growing quite large. Break that
relationship out into its own concept and give it a name.

Instead of being a singleton that represents the entire relationship
with the backend, the object is now per-customer (since any meaningful
method requires a customer anyway for the from JID at least) and can be
delegated to directly from Customer.

* invites:
  Block repeated invite code tries by customer id
  Allow user to activate using invite code

So it's not as trivial to brute-force the space and find an open one. Limit is
10 tries per hour.

Checks if the code is available and marks it used, then activates. Tracks who
invited and who used in the table for later reward or punishment.

* set-forwarding-on-finish:
  Configure number for inbound calls

* import-to-catapult:
  Import newly-purchased numbers to Catapult

* show-ratecenter-during-signup:
  Show rate center during signup

* activated-users-to-finish:
  Test that registered users get the Registered step
  Already activated user goes straight to finish

Fetch from bandwidth so we can show it to the user, in case they happen to care.

If not registered, but activated, they must have paid but failed to get their
number setup. Maybe the number was already taken. Maybe they paid manually. In
any case we can skip all intervening steps and go straight to buying and
configuring their number for them.