The bug of Convar "rd_drone_flinch_resets_attack"

[mengpotang-007]

Steam feedback discussions link(https://steamcommunity.com/app/563560/discussions/2/595139573830449159/)

In the previously closed issue, (#850)
found a bug about Convar "rd_drone_flinch_resets_attack". This Convar did not have a bug fix for drones being able to attack immediately after a flinch as stated in the update log.

update log：
rd_drone_flinch_resets_attack: New. Set to 1 to revert the bug fix for drones being able to attack immediately after a flinch even if their previous attack would not have finished. If you set this in a challenge, consider setting asw_drone_attack_speed_on_fire to the value of asw_drone_attack_speed (default 1.25) as well.

Added rd_drone_flinch_resets_attack for use in challenges. It returns drone flinching behavior to how it was in Alien Swarm, where it would cancel attack animation timers.

The values ​​1 and 0 in the update log are misplaced. According to the update log description:
Value 1: Enable the bug, allowing drones being able to attack immediately after a flinch.
Value 0: Enable the fixed bug, restore to the way it was in Alien Swarm.

Now let's compare the difference between AS and RD drone attacks.
AS: https://youtu.be/s0KzLRnryqE
RD: https://youtu.be/jtaHuoegswA

So I suggest fixing the error in the value of Convar "rd_drone_flinch_resets_attack". And made drone to drones being UNABLE to attack immediately after a flinch.