Add a function or option to swap the button assignments of 2 sticks or buttons

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Is your feature request related to a problem? Please describe.

This might be loosely related to #764, but only in the way that both features could rely on the same logic/function for moving button mappings around.

I would like to have a way to quickly swap assignments between 2 buttons or 2 sticks when defining profiles/mappings in the ui.

Simple example with sticks (buttons listed left, up, right, down):
Left stick: W A S D
Right stick: home end PgUp PgDown

select stick 1 or 2, then pick/activate the 'swap' feature and select the other as target
Expected result:
Left stick: home end PgUp PgDown
Right stick: W A S D

The swapping function should completely transfer any button mapping, regardless of whether it is a simple keyboard button or a macro etc.

Use cases i can think of:
1. It might be helpful for Left-Handed vs. Right-handed layouts, either when defining the mappings or as a dynamic option
2. Games where 'movement' and 'camera' can't be clearly separated, a bit of experimentation of what feels more natural is required. For that i wouldn't want to manually reassign back-and-forth. I'm aware i could just do this by creating 2 set or profiles with the sticks swapped for the experimentation. But that still requires both alternatives to be created first where the swapping logic would be a huge QoL improvement.
3. More convenience when creating a new profile from scratch as sometimes it turns out that the initially set up mapping doesn't feel as natural (or works as well) as thought. The keyboard keys and macros themselves would remain the same (as they depend on the game), but they'd be moved around to 'make more sense'.

I can also try to help with the implementation of the swap-function. But i'd need a few pointers on where to start looking as i'm not familiar with the antimicrox code.

### Describe the solution you'd like

_No response_

### Describe alternatives you've considered

_No response_

### Additional context

_No response_