transitional compliant
Original patch by chema@ximian.com, modified/extended by
bbaetz@student.usyd.edu.au
r=gerv, justdave

Patch by Christopher Aillon (caillon@returnzero.com). r1=Christian Reis (kiko@async.com.br),
r2=Zach Lipton (zach@zachlipton.com) though not really needed for this patch.

patches by zach@zachlipton.com. Thanks!

"editbugs" and "canconfirm".  People without these states are now much
more limited in what they can do.

For backwards compatability, by default all users will have the
editbugs and canconfirm bits on them.  Installing this changes as is
should only have one major visible effect -- an UNCONFIRMED state
will appear in the query page.  But no bugs will become in that state,
until you tweak some of the new voting-related parameters you'll find
when editing products.

now choose whether to let submitters of new bugs choose a priority, or whether
they should just accept the default priority (which is now no longer hardcoded
to "P2", but is instead a param.)  The default value of the params will cause
the same behavior as before.

some changes to the database schema!