Improve alias remapping

[TobiasFella]

• Don't print a warning if an alias is remapped from a room to its replacement room
• Don't remap aliases from the new room to the old room
  (I've never noticed any problems caused by this, but the log message is slightly annoying)

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
0.0% Duplication

[TobiasFella]

Sonar complains about "code complexity"; should i refactor the code a bit?

[KitsuneRal]

TL;DR: No; it's Sonar's fault, not ours.

I found some time ago that Sonar spins up complexity on every qC* macro (you can see it in the issue details). I used to switch to their q* counterparts in the past to avoid it (they also allow to specify logging categories since Qt 5.12 or something). I don't practice it any more because, as I mentioned in the chat one day, qC* versions force you to provide a category (a good thing) while q* don't; and this is more valuable than trying to go around quirks of a static analysis tool.

And after digging up stuff recently I learnt that Sonar actually tried to fix this very issue as long ago as in 2018 - yet somehow it's still here. Looking at the way it was fixed, I can imagine it still tries to account for "generated code" (as it's called inside Sonar codebase) in some place - so, see TL:DR.