When listing the branches available to take, rely on the status rather than the POC
Bump to 1.13 and update documentation accordingly
When giving a package, allow the user to specify more branches than the package has

This way in pkgdb-cli we can use all the active branches w/o having to
check what are the branches for each package.
Adjust the unit-tests for the new behavior of the /package/acl/reassign/ endpoint
Release 1.13.1 and adjust documentation accordingly
Fix api for orphan/unorphan/retire and reassign as set are not serializable to JSON
Release to 1.13.2 and adjust documentation accordingly
Restrict the list of groups asked at login
Release 1.13.3 and adjust documentation accordingly
When unorphaning a package, reassign the bugs to the new POC, not the person doing the action

Fixes https://github.com/fedora-infra/pkgdb2/issues/72
Update the email_publish method to accept a to_email kwarg

This will allow the email_publish method to send emails for other parts
of the code (for example the pkgdb2_branch.py script).
Update the pkgdb2.lib.add_branch method to return an information message upon success and failure
Add logic to send a summary report by email after the branching has occurred
Add the possibility to print the report instead of sending it by email
Not having a package specified is not enough to not send the email
Commit after having added all the new branches
Output a little information message in pkgdb2_branch before sending the email
Save the new branch to the database as we create them
Remove the commit at the end now that we commit as we go
Now that we save messages for successes as well as failures, no questions about returning them