Refactor PEM code to remove need for provider

With this chance, it is no longer necessary to register the
BouncyCastleProvider as a JVM-wide security provider in order to
read/write PEM files.  This eliminates the possibility that
the BC provider will be used for SSL operations where we are
not explicitly asking for it to be used (such as by Jetty,
when decrypting HTTPS requests).
Merge pull request #30 from cprice404/bug/0.1.x/dont-register-bouncycastle-security-provider

Refactor PEM code to remove need for provider
Update version number to 0.1.2 for release
Update version to 0.1.3-SNAPSHOT for development
Merge remote-tracking branch 'origin/0.1.x'

Conflicts:
	project.clj