[Payment Method Improvements] Implement record transaction details to order note functionality

[backwardstruck]

Closes: #11585

Description

This PR implements the functionality to record transaction details as an order note upon returning to the order screen after marking the order as complete.

Also updated the unit test based on this suggestion:
#11586 (comment)

And addresses feedback from this PR:
#11585

Testing instructions

1. Enable OTHER_PAYMENT_METHODS
2. Open an order and proceed to payment.
   • Choose the cash payment option.
   • Switch the Implement record transaction details to order note toggle to enabled (and try again without switching it)
3. Mark the order as complete

Expected:

• Ensure that order notes are added correctly for different amounts paid by the customer.
• Validate the correctness of the change due calculation in the note.
• Specifically, a note detailing "The order was paid by cash. Customer paid x. The change due was x." is added to the order to accurately capture the cash payment details.

Images

Addressed feedback so 16.dp is consistently used for horizontal padding across various elements to align them.
Used 8.dp or 16.dp for vertical paddings ensuring consistent spacing within the UI elements.
Ensured the 'Change Due' section and record transaction note have proper padding and spacing.

Aligned the button and input field using consistent horizontal padding.

Before	After

• I have considered if this change warrants release notes and have added them to RELEASE-NOTES.txt if necessary. Use the "[Internal]" label for non-user-facing changes.

[dangermattic]

	2 Warnings
⚠️	This PR is larger than 300 lines of changes. Please consider splitting it into smaller PRs for easier and faster reviews.
⚠️	This PR is assigned to the milestone 18.9. This milestone is due in less than 2 days. Please make sure to get it merged by then or assign it to a milestone with a later deadline.

	1 Message
📖	This PR contains changes to Tracks-related logic. Please ensure (author and reviewer) the following are completed: The tracks events must be validated in the Tracks system. Verify the internal Tracks spreadsheet has also been updated. Please consider registering any new events. The PR must be assigned the category: tracks label.

Generated by 🚫 Danger

[wpmobilebot]

📲 You can test the changes from this Pull Request in WooCommerce Android by scanning the QR code below to install the corresponding build.

	App Name	WooCommerce Android
	Flavor	Jalapeno
	Build Type	Debug
	Commit	a1e4a99
	Direct Download	woocommerce-prototype-build-pr11594-a1e4a99.apk

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 27.27273% with 24 lines in your changes are missing coverage. Please review.

Project coverage is 40.22%. Comparing base (5208114) to head (b607180).

❗ Current head b607180 differs from pull request most recent head a1e4a99

Please upload reports for the commit a1e4a99 to get more accurate results.

Files	Patch %	Lines
...hangeduecalculator/ChangeDueCalculatorViewModel.kt	28.12%	23 Missing ⚠️
...ts/methodselection/SelectPaymentMethodViewModel.kt	0.00%	1 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##              trunk   #11594      +/-   ##
============================================
+ Coverage     40.13%   40.22%   +0.08%     
+ Complexity     5219     5202      -17     
============================================
  Files          1093     1089       -4     
  Lines         63900    63523     -377     
  Branches       8793     8724      -69     
============================================
- Hits          25646    25549      -97     
+ Misses        35932    35670     -262     
+ Partials       2322     2304      -18     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[kidinov]

@backwardstruck 👋

In order to move forward and land it on the current release I

• Resolved merge conflicts
• Adjusted margins and some UI stuff
• Moved network call out from the main scope
• Added loading indicator to a button
• Removed unused nav action
• Made the release note public, not internal as this a user-facing change
• Color theme of the toggle (used to be red or something like that)

Feel free to revert/do any changes if that doesn't make sense to you

05-30--10-26.mp4

[backwardstruck]

Thanks a lot for the help! I checked all those changes you made. Some were pretty serious and I don't see any that need to be reverted.