Merge lp://staging/~jtv/launchpad/bug-592762 into lp://staging/launchpad

TeamMembership privilege for translationstobranch.

= Bug 592762 =

Sometimes the translations-to-branch exporter is asked to export translations to a bzr branch that doesn't exist. This is possible because the Code UI lets users "register" branches, which creates the branches in the database but not in bzr.

I fixed up the script to send out email notifications when this happens. But in Q/A I found that if the email recipient is a team, the email helpers need SELECT privileges for the TeamMembership table which the script currently lacks.

So here's the fix for that. As long as you don't re-build your schema first, this test reproduces the problem:
{{{
./bin/test -vv -t handleUnpushedBranch_is_privileged_to_contact_team
}}}

Run this to make the problem go away and the test pass:
{{{
./database/schema/security.py
}}}

To Q/A, all I have to do is inspect the logs on staging a day after this fix is rolled out and hopefully see the script complete successfully.

Jeroen