Add a leading 0. to the version to better handle releases

This fits a little better with semantic versioning, so:

* The **major** number is hard-coded to "0" for now, so if/when cjdns issues an
  official v1.0 release, it will be a newer release according to the package
  manager.

* The **minor** number is based on the number of commits, so this will
  always be increasing.

* The **micro** number is the short Git revision SHA1, so you can easily
  reference the exact commit each package was generated from.
Support building cjdns on the Raspberri Pi

The PR #1 only updated the cjdcmd PKGBUILD, but not the one for cjdns
itself, so this adds armv6h support to that as well.