Fixes Defiant interaction with Court Changed Sticky Web + Fickle Beam description

[PhallenTree]

Fixes Defiant/Competitive no longer working if the battler enters the field with a Court Changed Sticky Web on its side of the field. Adds test for this and for Defiant not triggering on Court Changed Sticky Web.

Fixes Fickle Beam's description's first line being too long.

Issue(s) that this PR fixes

Fixes #5086

Discord contact info

PhallenTree

[AlexOn1ine]

@PhallenTree I don't understand why it was broken and why this fixes it. Could you provide a small overview of the problem and fix?

[hedara90]

I was the one who reported the bug. I don't know why this fixes it (I haven't checked).
But the problem was:

• Player uses Sticky Web
• Someone uses Court Change to switch the webs to the player side
• Player switches in a 'mon with Defiant
• Defiant does not trigger from the speed drop from the webs (intended behavior)
• Further stat drops from opposing sources no longer triggers Defiant for the 'mon (bugged behavior)

[PhallenTree]

This bug occurs in the first place because gBattleScripting.stickyWebStatDrop gets set to 1 when a mon switches into Sticky Web and would only get set to 0 if Defiant/Competitive triggered. Since the value was 1, !(gBattleScripting.stickyWebStatDrop == 1 && gSideTimers[targetSide].stickyWebBattlerSide == targetSide) (which is the last condition to trigger Defiant/Competitive) would always fail as long as the target has a Sticky Web on its side of the field setup by its own side of the field. The fix sets gBattleScripting.stickyWebStatDrop to 0 once Sticky Web is done so that Defiant/Competitive continue working correctly afterwards.
I've replaced my previous fix with one which makes a bit more sense.