Switch to D-Base32 ID encoding, drop Python 3.2 support

[Jason Gerard DeRose]

So that we have a smaller target, and don't spend so much time maintaining back-ports, we're going to be dropping support for Precise and Quantal as we make the final steps toward Dmedia being production ready:

http://blog.novacut.com/2013/02/dropping-support-for-ubuntu-precise-and.html

One of the breaking changes will be switching from standard RFC-3548 Base32 encoding to our proposed D-Base32 encoding, the rationale for which is here:

http://docs.novacut.com/dbase32/design.html

The needed Microfiber changes are quite small. Although I want this waiting and ready, we wont merge this till we flip the switch from the version 0 protocol/schema to the stable version 1 protocol/schema.

(Note I filed this bug with `ubuntu-bug python3-microfiber` to test the changes I made in the Apport integration.)

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: python3-microfiber 13.02.0-0~raring
ProcVersionSignature: Ubuntu 3.8.0-6.11-generic 3.8.0-rc7
Uname: Linux 3.8.0-6-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
CrashDB: {'impl': 'launchpad', 'project': 'microfiber'}
Date: Tue Feb 12 02:19:35 2013
InstallationDate: Installed on 2012-08-06 (189 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: microfiber
UpgradeStatus: Upgraded to raring on 2013-02-01 (10 days ago)

[Jason Gerard DeRose (jderose)]

So I went ahead and merged this to trunk, and then switched back to standard Base32 encoding using the new compatibility functions in dbase32.rfc3548.

That way we can move forward with dropping Python 3.2 support and being as ready as possible to switch to D-Base32, even thought we're not quite ready to make the switch.