fix(DB/creature_loot) - Durar's and Kathorn's Power Cell corrected drop rate to 100%

[ovv]

Changes Proposed:

This PR proposes changes to:

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

Issues Addressed:

• Closes 19931

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). Cherry-picks must be committed using the proper --author tag in order to be accepted, thus crediting the original authors, unless otherwise unable to be found

1. https://www.youtube.com/watch?v=BlmOZ07UlG0
2. https://www.youtube.com/watch?v=g6YGyNQBE3Y
3. https://www.youtube.com/watch?v=b0Ytr2192M0

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. .quest add 12197
2. .go creature id 26409
3. kill and loot

Known Issues and TODO List:

/

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.

[heyitsbench]

Please use an update file instead of modifying the base queries. You can refer to other pull requests that edit the database as a guide, or use this wiki page.

[TheSCREWEDSoftware]

Do not update the base SQL.

sql\updates\pending_db_world

Is the place where you run the bash file (create_sql) and make your query there.

[TheSCREWEDSoftware]

Following the SQL standards: https://www.azerothcore.org/wiki/sql-standards you can use bench's PR as a reference how to do it: https://github.com/azerothcore/azerothcore-wotlk/pull/22124/files

Edit: If you find proof that Kathorn's Power Cell also should be a 100% you can update both. refering to this because the issued link refer to the other power cell.

[TheSCREWEDSoftware]

Use backticks for table name and column values as shown in the SQL standards.

Since they changes you're making is the same for both, you can have them in 1 query.