fix: prevent item dupe exploit on item swap

[Qwerty1Verified]

Description

This PR fixes a duplication exploit and stops the front-end from sending a custom item transfer amount when two items that aren't the same are being swapped. This amount is unneeded for this action since the two items can't be stacked by any amount and need to completely swap if they're two different items.

This PR also updates the server-side of this request by not using the amounts provided by the front-end for swapping, and instead using the back-end .amount values known to the inventory. This is because for completely swapping two items, the full amounts for both items should be swapped, and no values from the client should be trusted unless performing an item name check on that slot after removal.

This could also be fixed across the board with other changes and validation to some exports.

This PR addresses the duplication exploit issues: #569, #563

Checklist

• [x] I have personally loaded this code into an updated qbcore project and checked all of its functionality.
• [x] My code fits the style guidelines.
• [x] My PR fits the contribution guidelines.

[Qwerty1Verified]

New commit addresses another bug with the UI on give item displaying the item being removed despite no one being around. This is issue: https://github.com/qbcore-framework/qb-inventory/issues/567

[Qwerty1Verified]

Also addresses the duplication and UI issue https://github.com/qbcore-framework/qb-inventory/issues/563