[Bug Fix] Fix Lua Crash with Spell Blocked Event

[Kinglykrab]

Description

• A Lua crash was occurring because there was no indication the event_spell_blocked line existed, so when attempting to get the event's name by its ID it was failing per @KayenEQ's log.
• Occurred when resolving merge conflicts in the original pull request.

Log

[04-01-2024 14:08:10] [Zone] [Crash] C:\git-eqemulator\Server\zone\lua_parser.cpp (881): LuaParser::GlobalPlayerHasQuestSub 
[04-01-2024 14:08:10] [Zone] [Crash] C:\git-eqemulator\Server\zone\quest_parser_collection.cpp (229): QuestParserCollection::PlayerHasQuestSubGlobal 
[04-01-2024 14:08:10] [Zone] [Crash] C:\git-eqemulator\Server\zone\quest_parser_collection.cpp (185): QuestParserCollection::PlayerHasQuestSub 
[04-01-2024 14:08:10] [Zone] [Crash] C:\git-eqemulator\Server\zone\spells.cpp (3579): Mob::AddBuff 
[04-01-2024 14:08:10] [Zone] [Crash] C:\git-eqemulator\Server\zone\spell_effects.cpp (125): Mob::SpellEffect 
[04-01-2024 14:08:10] [Zone] [Crash] C:\git-eqemulator\Server\zone\spells.cpp (4526): Mob::SpellOnTarget 
[04-01-2024 14:08:10] [Zone] [Crash] C:\git-eqemulator\Server\zone\spells.cpp (2591): Mob::SpellFinished 
[04-01-2024 14:08:10] [Zone] [Crash] C:\git-eqemulator\Server\zone\spells.cpp (1743): Mob::CastedSpellFinished 
[04-01-2024 14:08:10] [Zone] [Crash] C:\git-eqemulator\Server\zone\spells.cpp (134): Mob::SpellProcess 
[04-01-2024 14:08:10] [Zone] [Crash] C:\git-eqemulator\Server\zone\client_process.cpp (500): Client::Process 
[04-01-2024 14:08:10] [Zone] [Crash] C:\git-eqemulator\Server\zone\entity.cpp (544): EntityList::MobProcess

Type of Change

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

Testing

@KayenEQ confirmed he no longer crashes with this fix implemented.

Checklist

• I have tested my changes
• I have performed a self-review of my code. Ensuring variables, functions and methods are named in a human-readable way, comments are added only where naming of variables, functions and methods can't give enough context.
• I own the changes of my code and take responsibility for the potential issues that occur