feat(order_details): Adding order_details both inside and outside of metadata, in payments request, for backward compatibility

[rishavkar]

Adding order_details both inside and outside of metadata, in payments request, for backward compatibility

Type of Change

• Bugfix
• New feature
• Enhancement
• Refactoring
• Dependency updates
• Documentation
• CI/CD

Description

Previously order_details was inside metadata as an object.
But we want to keep order_details outside metadata, as an array of objects.
So accepting both of these order_details, for backward compatibility.
If we accept order_details inside metadata in Payments_create, we also need to send it inside metadata for payment update and confirm, and vice versa.
Also, order_details cannot be passed both inside and outside metadata for payments request.

Additional Changes

• This PR modifies the API contract
• This PR modifies the database schema
• This PR modifies application configuration/environment variables

DB change: field "order_details" added to payment_intent
API contract change: payments request has an extra field "order_details"

Motivation and Context

How did you test it?

https://docs.google.com/document/d/18NuXDQdSGTIjpJsVULs19XQHNFmygdJdCPA8J5_PfJw/edit

Checklist

• I formatted the code cargo +nightly fmt --all
• I addressed lints thrown by cargo clippy
• I reviewed submitted code
• I added unit tests for my changes where possible
• I added a CHANGELOG entry if applicable

[Narayanbhat166]

There are few files which are conflicting, please resolve them.

[Narayanbhat166]

There are a lot of places where the clones can be avoided, since we are only checking if the value is present and not consuming it. You can instead use .as_ref() in those places