RedWarn QTs don't support abuse filters

Expected Behavior

RedWarn would post the message regardless of the abuse filter

Current Behavior

The QT task fails and leaves a console error.

Possible Solution

• Make RedWarn send the edit twice to ignore the filter
• Add a dialogue to make sure the user confirms what they are doing.

Steps to Reproduce

1. Install any QT pack that has templates that will trigger the abuse filter (I'm using this pack)
2. Try to use one of the templates
3. RedWarn will from an error saying to check the console.
4. Check console

Some information

N/A

Exception, error or logs

<!-- Please do NOT remove this header message. Thank you. -->
{{User:Sandbox for user warnings/Talk header}}
__TOC__
<!-- All comments/sections/warnings/etc. go below this line -->
==Notice==
{{subst:Ds/alert|IPA}} ~~~~       
index.php?title=User…ext/javascript:2744 
Object
error: {code: "abusefilter-warning", info: "⧼abusefilter-warning-DS⧽", abusefilter: {…}, *: "See https://en.wikipedia.org/w/api.php for API usa… notice of API deprecations and breaking changes."}
servedby: "mw1285"
__proto__: Object

Final checklist

• I have included the version of the browser I'm running, operating system and other scripts (if used). N/A
• I have included logs, exceptions and / or steps to reproduce the issue.

added priority::needs triage type::bug labels

removed priority::needs triage label

added priority::medium label

added state::to do label

assigned to @ChlodAlejandro

changed the description

Partially fixed by 9a689f99, however it relies on alert() instead of a proper RedWarn dialog. Because of this, I'll keep this issue open until it can be changed.

added state::partially done label and removed state::to do label

nts: add this patch in the dev_16.1 branch

and please turn it into a dialog instead of a bodged alert box uwu

@ChlodAlejandro ofc honestly the whole quick template thing is a mess that I wanna make a proper UI for eventually