Added Chat Filter functionality

[Adonca2203]

Added a chat filter setting which enables/disables chat filters for the local client.

There is a new json setting called "ChatSettings" which host a filter list as well as a boolean to enable/disable the feature (default disabled)

The feature can be enabled/disabled in the General Settings tab, you can add your own words to filter using regular string or regex as well as have a replacement word if you'd like to replace instances of the bad word.

This change is only reflected locally and not enforced lobby wide so everyone has their own filter list. There is a default list of words which got pulled in discord but these too can be removed.

Also did some cleaning up of removing unused dependencies in scripts.

[AutumnThyme]

I have an example program that you can use to validate your filters.
You may want to look to use this as a basis for your implementation though I have no idea what the performance is. Looking this up online, this seems to be a hard problem that most people have just left to report review and AI since analyzing text is hard.

The tl;dr/most important parts of this review are:
Load from a dedicated json resource file we include with the game, no hardcoding profanities in code.
Load profanity list on game start IF the user has it enabled -> do not waste memory/performance on a disabled feature.
Current implementation is a bit messy and not performant at scale, use example program as a basis for this (prioritize not doing a ton of string operations since C# is absolutely horrible at handling those)
Finally, ensure that the implementation does not break rich text formatting (honestly I have no idea how to handle this and its going to be an annoying task likely)

using System.Collections.Generic;
using System.Linq;
using System.Text.RegularExpressions;

public class ProfanityTest
{
    public static void Main(string[] args)
    {
        List<string> filters = new List<string>() {
            "\\bt\\w*st\\b",
            "\\b\\w*input\\b",
            "\\btha+t\\b",
            "\\bchecK\\b",
            "\\bis\\b"
        };
        string input = "This is a test input that we want to check for profanities. Let's commit to retesting to ensure only word against words are checked.";
        
        List<Regex> compiledPatterns = filters.ConvertAll(pattern => new Regex(pattern, RegexOptions.IgnoreCase));
        
        foreach (var regex in compiledPatterns)
        {
            input = regex.Replace(input, match => 
            {
                string word = match.Value;
                if (word.Length > 2)
                {
                    return word[0] + new string('*', word.Length - 2) + word[word.Length-1];
                }
                return new string('*', word.Length);
            });
        }
        
        Console.WriteLine(input);
    }
}

Expected Output:

This ** a t**t i***t t**t we want to c***k for profanities. Let's commit to retesting to ensure only word against words are checked.

[AutumnThyme]

What's with all the asset changes?

[AutumnThyme]

These should be loaded from a file, having this stuff hardcoded in the game is a bit weird and takes up unnecessary memory.

[AutumnThyme]

If you aren't getting a clean string from the json, there is an issue with your implementation.

[AutumnThyme]

We should pre-compile each regex if its going to be called on every message (ofc not pre-compiled if the setting is off otherwise this will use up memory)

[AutumnThyme]

I don't think this is really needed, we should just load this stuff like all other json files we load (think UI.Locale).
Optimally what I would want out of this is for us to potentially ship the game with a single "FilteredWords.json" file, this should include at most a list of string patterns and potentially a integer/float value for filter level.

On Game Join, if the setting is enabled, load the list into memory. Otherwise do not load it into memory and have the filter be a null check/quickly return each message as valid.

[AutumnThyme]

I would prefer if we use a more linq/C# approach to iterating over matches.
Likewise if we're allowing user defined patterns, then there can be any number of groups.
We should pick either a dedicated rule, 1 word/phrase per pattern. I should note that this also looks like its going to cause issues with word boundaries, basically a phrase containing profanity is not necessary profanity which means entries will need to either be defined correctly wrapping each with \b or we do this for the user (less control but less complaints about it not working)

[AutumnThyme]

Fix tabbing

[AutumnThyme]

We aren't targeting these platforms?