[Refactor] Refactor abort controllers to simplify creation/deletion

[arielj]

We have this pattern in a lot of places:

import {
  createAbortController,
  deleteAbortController
} from './utils/aborthandler/aborthandler'

...
...

const abortId = 'some-id'
runSomeCommand(
  ...
  createAbortController(abortId)
  {
    ...options
  }
)
deleteAbortController(abortId)

This PR is a refactor of that to only need the abortId when calling the functions and the abort controllers are created/deleted internally. It removes a lot of imports and explicit calls to createAbortController and deleteAbortController.

So now we don't need the imports and we can do

runSomeCommand(
  ...
  {
    abortId: 'some-id',
    ...options
  }

The abortId is also now optional, if we want to run something that we don't need to abort manually we can ignore that option.

We can still abort things when needed since the abort controllers are still being tracked and created with the same ID as before.

---

Use the following Checklist if you have changed something on the Backend or Frontend:

• Tested the feature and it's working on a current and clean install.
• Tested the main App features and they are still working on a current and clean install. (Login, Install, Play, Uninstall, Move games, etc.)
• Created / Updated Tests (If necessary)
• Created / Updated documentation (If necessary)

[arielj]

if no abortId is passed, it tries to get the appName from the command, else it generates a random id

[arielj]

since the abortId is release.version, I'm just reading that inside installWineVersion so no need of a parameter, but it's created the same way as before

[flavioislima]

Codewise looks good. It is just a lot of places to test so it is more likely we find bugs after the next release with this change.
although looking at the code I think everything will be fine.

[arielj]

I'm merging this, I tested a lot of things and if we get this merged we can have more developers testing before a release

I don't want to start getting conflicts