This allows a customer to change their JID, but it's a bit raw.
In practice I don't expect anyone to actually run this directly, instead
cheogram covers with with a friendlier and safer version.

This is just the business.

* block-calls-when-expired:
  Block voice calls when account is expired
  Refactor CallAttempt factory to use registration pattern

This reverts commit 36f441c031a5318385ec78d7d2e021a8e2fab186, reversing
changes made to 3b0ae3c9387d3be41b30bd6dd4552ff0a841d8ed.

* three_d_secure:
  Send 3DS id when making a transaction

Allow for "transitional" (no plan) users for now, because we still have a bunch
of those.

* change-billing-lock:
  ExpiringLock instead of require expired
  Atomic ExpiringLock

We *want* to try billing a little before expiry, to prevent the account lapsing.
So use an ExpiringLock to prevent double-billing races.

* only-bill-if-expired:
  Only bill customer if they for sure have balance and are expired
  Allow an in-transaction condition for billing
  Change multiline chain style

* sip-concurrency:
  Limit call concurrency for outbound SIP

* fwd-cleanup:
  Try to classify URI before saving, even if timeout.zero?
  v1 is dead and everyone has been moved
  Allow finishing adming command

To allow building from a hash with extra keys. Makes the CustomerRepo more readable.

Helper for queries that only return a single row.

* max-call-length:
  Calculate the maximum allowable call length

* credit-card-blacklist:
  Credit card blacklist

Any card on the list is just treated as though it is not present, preventing it
from being used.

Asterisk could use this to actually limit the call, for example.

* trustlevel-repo:
  TrustLevel{,Repo}

To determine how much permission a customer account should have to take risky
actions.  Seperate from their plan, this is not how much they could do in
theory, but how much the system will allow in practise due to perceived risk.

Starts out with a simple model based on amount of settled payments, and being
used to decide what is an "expensive" route for outbound calls.

* insert-settled-after:
  Credit card transactions settle after 90 days, bills instantly

* bill-with-note:
  Add a note when billing account

* activate-with-balance:
  If customer already has enough balance, just bill them and finish
  New BillPay registration step
  Save plan to DB as soon as it is selected
  Move credit_to lookup into relevant class

Assumes they have enough balance (anyone using this step must be sure of this)
and then does the billing before proceeding to finish.

Customer will appear as instantly expired (having been active for 1 second in
the immediate past).

This can replace the pending_plan key for BTC activations. It also serves as a
record for mail-in activation of what plan they had selected.

Once the account is really activated the tiny row is removed.

* monthly-billing:
  Allow the DB to notify us to bill a customer
  Command.execution setter
  Bill plan command
  Clearer name for lock bypass factory

Implements the full logic of the billing_monthly_cronjob for one customer by
reusing code that has been written more robustly in sgx-jmp for some time.  This
will allow the cronjob to just execute this command once a day for each expiring
customer to get all the correct billing behaviours.