Add to documentation that Brave Browsers should use the "chrome" install.sh option

[CrazyPython]

This is the patch I used to get TabFS functioning with Brave:

-              ( "$1" == "chromium" && "$#" -eq 2 && ${#2} -eq 32 ) ) ) ]]; then
-    echo "Usage: $0 <chrome EXTENSION_ID | chromium EXTENSION_ID | firefox>"
+              ( "$1" == "chromium" && "$#" -eq 2 && ${#2} -eq 32 ) || 
+              ( "$1" == "brave" && "$#" -eq 2 && ${#2} -eq 32 ) ) ) ]]; then
+    echo "Usage: $0 <chrome EXTENSION_ID | chromium EXTENSION_ID | brave EXTENSION_ID | firefox>"
    exit 2
fi
    
@@ -32,6 +33,8 @@
        MANIFEST_LOCATION="$HOME/Library/Application Support/Google/Chrome/NativeMessagingHosts";;
    "Darwin chromium")
        MANIFEST_LOCATION="$HOME/Library/Application Support/Chromium/NativeMessagingHosts";;
+    "Darwin brave")
+        MANIFEST_LOCATION="$HOME/Library/Application Support/Google/Chrome/NativeMessagingHosts";;
esac

As you can see Brave installs to the same place as normal Chrome, instead of its own Brave-Browser/NativeMessagingHosts.

I think it would be helpful to update your documentation site to note that Brave users should use the chrome option.

Citation: https://support.1password.com/could-not-connect/

[CrazyPython]

I almost submitted a pull request to add a mkdir -p for MANIFEST_LOCATION, but the code already has that– so this would work.