New List Filter Pagination Fields Has Encoded Fields Which Results in Empty Results for page 2+

[Powellze]

@nozzlegear
Latest release V5.0.3
When using fields on the filter, the nextPageFilter encodes ',' as %2C, this results in the next page results pulling through with no fields selected.

For now i'm having to use your first code snippet of usage rather than the new suggested approach.
// bug with fields being encoded by shopify
newFilter.Fields = newFilter.Fields.Replace("%2C", ",");

See encoding issue:

See code i've used which works in production right now based upon your first iteration of recommended usage:
`
var hasNextPageResults = true;
var page = 1;

        while (hasNextPageResults)
        {
            ListResult<Order> result = await service.ListAsync(listFilter);

            Console.WriteLine($"Received page {page}");
            if (result.LinkHeader?.NextLink != null)
            {
                var newFilter = result.LinkHeader.NextLink.GetFollowingPageFilter();
                // NOTE: For now, you must set the limit and fields property for further page filters manually.
                newFilter.Limit = filter.Limit;
                // Set the filter to the following page filter, which will grab the next page.
                // Failure to do this will result in an infinite loop as the Shopify API returns the first page over and over

                // bug with fields being encoded by shopify
                newFilter.Fields = newFilter.Fields.Replace("%2C", ",");

                listFilter = newFilter;
            }
            else
            {
                hasNextPageResults = false;
            }

            items.AddRange(result.Items);

            if (items.Count > maxOrdersToReturn)
                hasNextPageResults = false;
            page++;

        }`

[clement911]

See #470

[nozzlegear]

Merged #470