Do not mark as 'patrolled' when adding CSD tag

[Insertcleverphrasehere]

Per this discussion: https://en.wikipedia.org/wiki/Wikipedia_talk:New_pages_patrol/Reviewers#Should_we_stop_marking_articles_tagged_with_CSD_and_PROD_as_'reviewed'_now_that_we_can_filter_them_in_the_NewPagesFeed?
We are going to stop marking CSDs and PRODs as 'reviewed' in the new pages feed at New Page Patrol, to stop things falling through the cracks if the CSD tags are inappropriately removed or the PROD removal is missed.

Twinkle currently does not mark PRODs as 'patrolled' but does mark CSDs as 'patrolled'. We need this to change so that CSD's are no longer marked as 'patrolled'.

[Insertcleverphrasehere]

To clarify, I know that this is toggle-able in the preferences pane, but this should be the default behaviour.

[Amorymeltzer]

@atlight Is this really as easy toggling L145 of twinkle.js? AFAICT, no pages exist with "markTaggedPagesAsPatrolled": true (which makes sense) so in theory, yeah?

[QEDK]

@Amorymeltzer defaults aren't stored in user Twinkle prefs .js I think. It should be as simple as the change you suggested.

[QEDK]

Currently, patrolling is enabled for CSD, XfD and tagging. The commit addresses CSD defaults per the RfC.

[QEDK]

@MusikAnimal this can be closed.

[Amorymeltzer]

@QEDK In the future, if you write "Closes ####" or "Resolves ####" in your PR, it will happen automatically. See https://help.github.com/articles/closing-issues-using-keywords/

[QEDK]

@QEDK In the future, if you write "Closes ####" or "Resolves ####" in your PR, it will happen automatically. See https://help.github.com/articles/closing-issues-using-keywords/

Righttt, I was under the idea only collaborators have that particular ability. Thanks!