feat: make fiat change non-breaking

[dino-rodriguez]

High Level Overview of Change

Updates public API response to intelligently decide on ACH vs. FIAT
depending on whether the request is a 1.0 or 1.1 response.

Rolls forward the PayID protocol server version to 1.1.

Context of Change

Makes ACH -> FIAT addressDetailsType change non-breaking.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor (non-breaking change that only restructures code)
• Tests (You added tests for code that already exists, or your new feature included in this PR)
• Documentation Updates
• Release

Before / After

We know do some backwards compatibility stuff.

Test Plan

I fixed all existing tests, but need to add more test coverage now in a
subsequent PR.

[nkramer44]

v1.1.0 uses AchAddressDetails right? If so, I think it should be "if not v1.0.0 or v1.1.0, send FiatAddressDetails, otherwise send AchAddressDetails". Could be wrong, but I think the way you have it squeezes the change into v1.1.0, making v1.1.0 backwards compatible with v1.0.0, not v1.2 backwards compatible with v1.1.0.

[nkramer44]

Disregard my last comment. All these different versions are tough to keep straight.

[0xASK]

LGTM!