definte MAX_COMMUNITY_USERS for use in testing
charging for all users actually means all unarchived users. glad we cleared that up again.
generator of domain for each product_type
generator for creating active users in excess of the community user limit
don’t memoize these, let django do the caching (accounting)
also assert that for an invoice created, the domain under the subscription’s subscriber is what we expect
test invoices for domains that have no current subscription but incur charges according to the community plan
we always expect to get one result for all of these (accounting tests)
test the product line item for the community invoice
we don’t actually have to go through all of the users and delete them here
test user line item for community invoices
test the sms line item for community invoices
Merge pull request #2156 from dimagi/accounting-community-tests

Tests for the Community Plans / Invoices