Allow open parentheses before cite: "(>>1"

[discomrade]

Allows cite regex to match a post number after an opening parenthesis. "I like the comfy threads (>>1 and >>2) because they're comfy"

From fallenPineapple@d78254b

side note: I believe the other change they did to the regex is logically equivalent, although the other refactoring may be worth considering.

[ctrlcctrlv]

I'm not likely to ever accept changes to the complex regexes in Vichan†. Someone else would need to take over maintainership burden. The existing ones have proven secure if not in all respects useful. The insane regexes in this software lead to many very subtle ways to create security compromising bugs. If the cite engine was replaced with one that was provably correct and not regex based I might consider that but that's a tall order.

† For non-security reasons.

[ctrlcctrlv]

Added to README:

3256049

[ctrlcctrlv]

• fe3e499
  

  vichan/static/unapplied patches/5d31f3bab70de7f983fd56aa18817ede38d1d4f3.patch

  Lines 2 to 5 in fe3e499

  	From: discomrade <83621080+discomrade@users.noreply.github.com>
  	Date: Thu, 12 Jan 2023 10:16:15 +0000
  	Subject: [PATCH] Add open parentheses to cite regex

[basedgentoo]

I feel like this would be a good addition. In testing it works fine. It's a tiny change, but it's a good one.
I feel that the regex should be reviewed by someone with a deep understanding before it is merged, however.
Also, merging this would let us delete the "unapplied patches" directory and free up some bloat from the README.
I personally don't feel "unapplied patches" should be a thing. That sort of thing should be a configuration options that you can choose from inc/instance-config.php or just not merged because it's decided to be pointless.

[ctrlcctrlv]

Unapplied patches made perfect sense when the project was unmaintained.

[ctrlcctrlv]

And, I think this is safe but I can't guarantee that obviously. The cites system is insane.