Refactor battle log code and message display logic

[coderabbitai]

Background

The current battle log system is overly convoluted and difficult to maintain.

Issues

• The message display logic uses confusing parameters ( and )
• Inconsistent formatting and priority calculations throughout the codebase
• Repetitive code patterns for adding messages to the battle log
• Unclear relationship between message size, priority, and visual representation

Proposed Solution

Refactor the battle log system to:

• Use a more intuitive API for message creation and display
• Create a consistent approach to message prioritization
• Improve readability of the battle log code
• Consolidate message creation into reusable functions

References

• PR discussion: feat: Psychic system overhaul P1 #424 (comment)

Notes

This issue was created as a follow-up to initial improvements made in PR #424, which introduced an function as a first step toward cleaning up this code.