Configuration support for Mathematics/CRUDE

[LordFarin]

Starting January 23, we as the CRUDE community (CRUDE is the Mathematics counterpart of SOCVR) have been in touch with the SOCVR community regarding automation/simplification of certain tasks. Cf. the chat transcript starting here. Thanks to @makyen for supporting us thus far!

These discussions have resulted in CRUDE desiring to be included in the configuration of the following userscripts:

• CVRG
• CVRA
• URRS (nice-to-have)

subject to the following configuration:

• Site: https://math.stackexchange.com | Mathematics
• Main room: https://chat.stackexchange.com/rooms/2165 | CRUDE
• Archive room: https://chat.stackexchange.com/rooms/88696 | CRUDE Archive

An initial attempt to configure this can be found here.
However we have since found out that there are more feature-rich alfa/beta versions of the scripts, which we would like to use.

In order to simplify things as much as possible, we are willing to conform to existing standards regarding the tags used and the format of the requests posted in the room. Any changes are nice-to-have, and might be part of feature requests.

However what is essentially different in CRUDE from SOCVR, as far as we understand, is that CRUDE also has a strong focus on deletion rather than only closing.

This issue was created to streamline the process. If there is any way we could help in setting this up, this would be great.

[makyen]

As of this point, both the alpha and release versions of the Request Generator, along with the Request Archiver have been updated to include full support for CRUDE, CRCQR, and The Tavern.

In addition, the beta version of the Unclosed Request Review Script (URRS) has been moved to release, which decouples the significant changes made in that version from the changes necessary to support additional rooms. Adding support for additional rooms to the URRS will be worked on next.

[makyen]

In the meantime there is a CRUDE-only version of the URRS. While the effects of the changes in that branch will be maintained when the URRS is adjusted to handle multiple sites, much of the actual code in that branch isn't written in a way that it can be directly incorporated into a version which is functional across multiple sites.