$location.search(search, [paramValue]) documentation now reflects that paramValue can be a Number

I've amended the documentation to reflect that paramValue can also accept a ```Number``` as the value to set in the same manner it currently accepts a ```string```.  I'm aware of it being used like this at present (without issue that I'm aware of) and so this PR just makes it a recognised usage of the API.