Fixing an uncaught ArgumentNullException that is thrown when 'RestClient.EncodeParameters()' tries to 'UrlEncode()' null values

Currently, it is possible to do this:

```C#
restRequest.AddParameter("name", null);
```

However, when `restClient.Execute(restRequest)` is called and the code reaches the `StringExtensions.UrlEncode()` extension, an `ArgumentNullException` is thrown because the parameter's value is `null`. This makes absolutely no logical sense, and is bound to confuse the end-user (including yours truly).

This patch works around this problem by encoding only the parameter name and simply ignoring the `null` value.

```C#
restRequest.AddParameter("first", "value");
restRequest.AddParameter("second", null);
restRequest.AddParameter("third", null);
restRequest.AddParameter("last", "least");

// output query string:    first=value&second=&third=&last=least
```

EDIT: fixed a copy-paste-programming error in the example