perf: remove unnecessary event callbacks

[dudantas]

Description

Removed Lua callbacks from MonsterType of various monsters. These callbacks were empty, which meant the functions were still being "called" by the monsters without performing any action, creating a significant performance bottleneck.

Removed the onHear event callback, which had a significant impact on the server and was not used anywhere. It executed the onHear callback for each spectator, causing an unnecessary overload without any real benefit, especially as we have other methods to check for these events.

Additionally, the monsterOnSpawn event callback was removed and replaced with MonsterType::onSpawn, which is much more efficient since it only needs to be declared in the script for each monster that actually uses it.

Finally, the way setRewardBoss was handled was improved. Previously, it was executed in an onSpawn event callback, but now it is done directly during the parsing of each monster script, marking them as reward bosses at the time of script loading, improving efficiency.

Behaviour

Actual

• Empty callbacks were being called by monsters without doing anything, causing a performance loss.
• onHear was executed for every spectator, generating unnecessary server overload.
• setRewardBoss was done through the onSpawn event callback, which was inefficient.

Expected

• Remove empty callbacks to avoid unnecessary calls and improve performance.
• Remove the onHear event callback to reduce overload and improve server efficiency.
• Use MonsterType::onSpawn to replace monsterOnSpawn.
• Set setRewardBoss directly during the reading of the monster scripts to avoid overhead during spawn.

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested

Tests were conducted to verify the effectiveness of the changes in terms of monster performance and behavior.

• Test A: Removal of empty callbacks and monitoring of performance.
• Test B: Verification of monster behavior with MonsterType::onSpawn.

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I checked the PR checks reports
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud