fix(Script/DB): Add Oathbound Warder pet abilities

[blinkysc]

[!] Please Read! This PR comes from AI with MCP

Changes Proposed:

Adds npc_oathbound_warder script that sets up player-controlled pet action bar spells for Oathbound Warder (30270) summoned by Horn of the Peaks (item 42840).

The pet is fully passive and only casts spells when commanded by the player.

• Core (units, players, creatures, game systems).
• Scripts (bosses, spell scripts, creature scripts).
• Database (SAI, creatures, etc).

Issues Addressed:

• Closes [StormPeaks Quest] Oathbound Warder summons lack their abilities #24061
• Closes Oathbound Warder summons lack their abilities chromiecraft/chromiecraft#8529

SOURCE:

The changes have been validated through:

• Live research (checked on live servers, e.g Classic WotLK, Retail, etc.)
• Sniffs (remember to share them with the open source community!)
• Video evidence, knowledge databases or other public sources (e.g forums, Wowhead, etc.)
• The changes promoted by this pull request come partially or entirely from another project (cherry-pick).

Tests Performed:

This PR has been:

• Tested in-game by the author.
• Tested in-game by other community members/someone else other than the author/has been live on production servers.
• This pull request requires further testing and may have edge cases to be tested.

How to Test the Changes:

• This pull request can be tested by following the reproduction steps provided in the linked issue
• This pull request requires further testing. Provide steps to test your changes. If it requires any specific setup e.g multiple players please specify it as well.

1. .go creature id 30295 (Thorim)
2. .quest add 13005 (The Earthen Oath)
3. Use Horn of the Peaks item to summon Oathbound Warder
4. Verify pet action bar shows 4 spells: Lava Burst, Earth's Grasp, Earth Shield, Earth Shock
5. Cast spells on a target - pet should cast and remain passive (no auto-attack)

Known Issues and TODO List:

• None

How to Test AzerothCore PRs

When a PR is ready to be tested, it will be marked as [WAITING TO BE TESTED].

You can help by testing PRs and writing your feedback here on the PR's page on GitHub. Follow the instructions here:

http://www.azerothcore.org/wiki/How-to-test-a-PR

REMEMBER: when testing a PR that changes something generic (i.e. a part of code that handles more than one specific thing), the tester should not only check that the PR does its job (e.g. fixing spell XXX) but especially check that the PR does not cause any regression (i.e. introducing new bugs).

For example: if a PR fixes spell X by changing a part of code that handles spells X, Y, and Z, we should not only test X, but we should test Y and Z as well.