Orbital: Fix customer profile auth/purchase

This commit should fix an issue when authorize/purchase calls were failing with error:

    <ProcStatus>841</ProcStatus>
    <StatusMsg>Error validating card/account number range</StatusMsg>
    <ProfileProcStatus>9576</ProfileProcStatus>
    <CustomerProfileMessage>Profile: Unable to Perform Profile Transaction. The Associated Transaction Failed. </CustomerProfileMessage>

when they are made using stored customer profiles.

[Orbital Gateway XML Interface Specification](https://secure.paymentech.com/developercenter/catalog/files/file?fid=%0A56O7b2gvI%2Bg%3D%0A) specifies:

> When using a Profile, set this field to `EMPTY` or nill-fill:
> `<CustomerProfileFromOrderInd>EMPTY</CustomerProfileFromOrderInd>`

Closes #1370.
Work around obsolescence of URI.encode

We do this by using the underlying parser directly, bypassing the
warning, but more importantly depending on still-supported
functionality.

Also fixes a few other warnings that have cropped up.
Finansbank: Update test url

Closes #1376.
Payex: Fix expiry month to allow 4 digit year

Closes #1377.
Cashnet: Allow overriding custcode

Closes #1378.
Pin: Update display name

Closes #1379.
Cashnet: Fix overridding item_code per transaction