fix(DB/SAI) - Fixes quest Counterattack! sometimes not being completed and adds 1 ability to the creature.

[TheSCREWEDSoftware]

Removes NOT_REPEATABLE and WHILE_CHARMED event_flag, allowing to always drop the flag no matter if it's CC'd or not from Warlord Krom'zar

and

Adds Strike to the Warlord Krom'zar sniffed from: 4.4.1.58158 and 1.15.5.57979

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 [Quest] Counterattack! (4021) - Banner (Object 164690) not spawning #21007
• Closes [Quest] Counterattack! (4021) - Banner (Object 164690) not spawning chromiecraft/chromiecraft#7404

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

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.

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.

[TheSCREWEDSoftware]

@Exitare if you want to give a test it should always drop the flag. My testing was done via .npc add temp 9456 indifferent if you have .quest add 4021

[Kitzunu]

Back ticks

[TheSCREWEDSoftware]

Done

[TheSCREWEDSoftware]

Also changed from 2 indiviual values to grouped