Backend: redo the player name formatter with components

[NopoTheGamer]

What

cus i felt likt it
still has issues not yet fixed

Changelog Fixes

• Fixed something in Player Name Formatter. - nopo

Changelog Technical Details

• redid the code for player name formatter. - nopo

[github-actions]

I have detected some issues with your pull request:

Body issues:
Change should start with a capital letter in text: redid the code for player name formatter.

Title issues:
PR title must include category 'Fix' if there are any fixes in the PR

Please fix these issues. For the correct format, refer to the pull request template.

[github-actions]

10 Detekt Failures

Rules flagged (4): Indentation, Wrapping, UnsafeCallOnNullableType, MaxLineLength
Files flagged (2): PlayerNameFormatter.kt, PlayerChatManager.kt

Rule violations

• PlayerNameFormatter.kt#L266 Indentation: Unexpected indentation (16) (should be 8)
• PlayerNameFormatter.kt#L270 Indentation: Unexpected indentation (14) (should be 8)
• PlayerNameFormatter.kt#L276 Indentation: Unexpected indentation (14) (should be 8)
• PlayerNameFormatter.kt#L282 Indentation: Unexpected indentation (15) (should be 8)
• PlayerNameFormatter.kt#L168 Wrapping: Missing newline after "{"
• PlayerNameFormatter.kt#L72 UnsafeCallOnNullableType: Calling !! on a nullable type will throw a NullPointerException at runtime in case the value is null. It should be avoided.
• PlayerNameFormatter.kt#L73 UnsafeCallOnNullableType: Calling !! on a nullable type will throw a NullPointerException at runtime in case the value is null. It should be avoided.
• PlayerChatManager.kt#L271 UnsafeCallOnNullableType: Calling !! on a nullable type will throw a NullPointerException at runtime in case the value is null. It should be avoided.
• PlayerChatManager.kt#L313 UnsafeCallOnNullableType: Calling !! on a nullable type will throw a NullPointerException at runtime in case the value is null. It should be avoided.
• PlayerNameFormatter.kt#L168 MaxLineLength: Line detected, which is longer than the defined maximum line length in the code style.

[hannibal002]

Moving to draft.

There's commented-out code that needs to be either properly ported or removed, throw Error() should use ErrorManager, and the PR description needs to explain properly why we change this and mention the known remaining issues properly.