OBLS-736 Add create transfer feature

[olewandowski1]

https://openboxes.atlassian.net/browse/OBLS-736

Adds a self-contained "Create Transfer" flow to the mobile app, reachable from a new dashboard tile. Lets a warehouse user scan a product or bin, pick an inventory item, enter a quantity, choose a destination bin, and complete the transfer.

Summary

• New dashboard tile Create Transfer opens a 4-step flow:
  • Entry - scan product or bin barcode, or search via the modal.
  • Item list - candidate InventoryItem rows (product · bin · lot · qty) filtered by the resolved product/bin, with a debounced filter input.
  • Quantity - read-only context panel + numeric input capped at the inventory item's quantityNotPicked.
  • Destination - destination bin scan/search, then submit.
  • Complete - one-tap PUT to flip the PENDING transfer to COMPLETED, success morphs the button to "New Transfer".

Kazam_screencast_00071.mp4

[jmiranda]

@olewandowski1 This looks great. The lag on the internal locations search should be looked into. If that's actually sloweness on the API, can you create a ticket for that and provide some details (re: steps to reproduce, timing, response size, etc) and then assign to me to provide acceptance criteria?

[jmiranda]

@awalkowiak this is merge-able from my perspective.

[olewandowski1]

@olewandowski1 This looks great. The lag on the internal locations search should be looked into. If that's actually sloweness on the API, can you create a ticket for that and provide some details (re: steps to reproduce, timing, response size, etc) and then assign to me to provide acceptance criteria?

@jmiranda This lag on video actually might be connected to my dev env, I had many stuff up and running and it looks like it could be my fault. I did check it again on fresh setup and it takes 1-2s to load, and it should be even faster on physical devices. There were also threshold improvement that should help prevent loading large datasets: https://openboxes.atlassian.net/browse/OBLS-744. That said, if you thiink 1-2s is still something we might want to improve, let me know and I'll create a ticket with as much detail as I can.

[jmiranda]

@olewandowski1 Thanks for the update. 1-2 seconds is fine-ish, but there's always room for improvement. I'll create a general ticket for evaluating performance for all screens / endpoints. We can take a systematic approach to make sure we don't get surprised.

Edit: I created a new ticket to capture performance metrics in logging and maybe using NewRelic/Sentry if time permits.
https://openboxes.atlassian.net/browse/OBLS-758