Support arbitrary float or int in URLs

This MR fixes #20 (closed) by removing the numerical type matching for URLs, since float doesn't also accept int and we don't want to encode every possible permutation (not that many, but the principle stands), so, just use string (default) and handle it later.

requested review from @duncan.meacher

added 5 commits

• 4d0311dd...120cbb79 - 3 commits from branch computing/gwdatafind:master
• 5d197789 - tests: add regression test for #20 (closed)
• ebf50ac1 - api.v1: don't presume int or float in URLs

Compare with previous version

merged

mentioned in commit 00029f1b