GraphQL updates for payments

You can now manage payments throughout the lifecycle of an order with our newly updated payments data model. Read more about what's new and how to start in Overview of Payments in Fluent.

The `FinancialTransaction` entity has been improved with the following:

• Accepts an optional list of `attributes` so that you can include necessary metadata related to your business for a given transaction
• Includes two new fields for interacting with the `amount`. Both `unscaled` and `scaled` integer fields have been added to enable more precision when performing calculations using the transaction.
• Has a connection to the `Payment` entity
• Added a new mutation `updateFinancialTransaction,` which allows you to update the `status` of a given `FinancialTransaction`
• `status` is now a `string` instead of an `enumeration`

The `Payment` entity has been improved with the following:

• Includes a connection to:
• `FinancialTransaction`
• `Fulfillment`
• `CreditMemo`
• Each connection has a reverse relationship, allowing you to connect back to the payment

The `Order` entity has been improved with the following:

• `FinancialTransaction` can now be created alongside the `Order` using the `CreateOrder` mutation to simplify the process of managing order orchestration,
• `Order` now takes an optional `BillingAddress` so that you can specify a different billing address than the one saved against the customer's billing account.

The `Inventory Position` entity has been improved with the following:

• Now, it has connections to the `product` and `location` entities. You can derive Product and Location information directly from the `InventoryPosition` query.
• FulfilmentChoice now optionally takes an array of attributes as originally intended; previously, only one was accepted.
• The `firstName` field in the GraphQL CreateCustomerInput schema is now optional.