libsecp256k1 integration

@sipa suggested I go ahead and PR this to get discussion going. It's his work, I've just integrated it into our build-system.
This was done in a few stages:
- Add libtool dependency. I've tried to update all relevant docs, but very possible I missed some. Note that we don't actually make real use of libtool yet, it's only used when linking the subproject.
- Pull in libsecp256k1 subtree
- Add configure option "--enable-libsecp256k1". This is disabled by default.
- Update the makefiles to link against the lib where necessary
- Finally, add in the actual implementation.
LevelDB shouldn't be subtree'd either. If you want to tie release code to a specific version, just put it in the configure.ac as a requirement... but that's a bad idea IMO. Especially for libsecp256k1 since upstream understands consensus-critical needs.