fix getChild before rageshake setup

[toger5]

Content

Fix missing logs in rageshakes. (yes there was another issue, the first one was using the same rageshake db as EW)
The issue:

• rageshake loggers are setup on the root logger via the rageshakes file init() method.
• files that used const logger = rootLogger.getChild("[childscopename]"); often executed before the init call.
• so the logger would be created before the parent logger got configured to use the rageshake log extension.
• we ended up missing a large amount of logs

Motivation and context

We need those logs. This Issue revealed the missing logs:
#4087
(we first got locally recorded logs from android via logcat and then a rageshake.)

Tests

uploaded logs before this change:
https://github.com/element-hq/element-call-rageshakes/issues/16750

• [CallViewModel] is missing [CallViewModel localTransport$] Creating item with keys compatibility ... does exisint but that is from the item with keys logging... not the getChild one

after changing some (first commit):
https://github.com/element-hq/element-call-rageshakes/issues/16754

• [CallViewModel][1783444309670] exists!!
• but [InCallView] is missing

after updating all logs:
https://github.com/element-hq/element-call-rageshakes/issues/16755

• we should have all logs now. including [InCallView] (only gets logged on fatal errors so not visible in rageshake)

Checklist

• A linked, pre-approved issue exists for this feature or UI change.
• I have read CONTRIBUTING.md in full.
• Pull request includes screenshots or videos for any UI changes.
• Tests written for new code (and existing touched code where feasible).
• Linter and other CI checks pass.
• I have licensed the changes to Element by completing the Contributor License Agreement (CLA)

[Johennes]

Oh wow, nice find! And amazing that this even adds a lint rule to prevent future regressions. ❤️