Coherent purpose for asadb/util/

[adehnert]

At the moment, asadb/util/ seems to be used for two things:

• random utility libraries for the DB
• executable scripts for the DB

These two roles should be moved to different locations. util/ could continue to fulfill one of these, or they could both be moved.

[adehnert]

My current thinking is to make util/ be Django library stuff, and bin/ (which would be new) and the individual app directories be random executables.

The split would be:

util/db_form_utils.py -> stay
util/dump_group_perms.py -> groups/ (justification: groups/migrations/0016_create_auth_groups is based on it)
util/emailbackend.py -> stay
util/emails.py -> stay
util/export_website_groups.py -> groups/
util/import_db.py -> groups/
util/__init__.py -> stay
util/mailman.py -> stay
util/migrations.py -> stay
util/misc.py -> stay
util/previews.py -> stay? forms?
util/sync_moira_authz.py -> bin/, or possibly upstream it in snippets and move it to mit/...
util/update_old_previews.py -> forms

(And *.sh and static-data would move to bin/ as well. Though maybe not if dump_group_perms.py is moving to groups/, which suggests maybe I shouldn't do that move...)

Though, hmm, making bin/ empty and moving executables in util/ to the app directories doesn't require much of a stretch... That's awfully tempting...