Let's make Greaselion more informative for debugging!

[mrose17]

Description

At present, the only diagnostic logging occurs when there's an error in Greaselion.json

...:ERROR:greaselion_download_service.cc(234)] Failed to parse Greaselion configuration

Otherwise, everything is silent. It would make debugging Greaselion issues a lot easier if these additions were made when running with --enable-logging --v=1:

1. when there is a match against an element in the urls array for a rule, there is a log entry
2. if one of entries in the preconditions array fails, there is a log entry indicating the offset of the array failed
3. otherwise, for each entry in the scripts array, there is a log entry indicating that the script was loaded and whether there were any errors (or not).

Steps to Reproduce

Go to a URL that invokes Greaselion. There is no diagnostic logging.

Actual result:

Go to a URL that invokes Greaselion. There is no diagnostic logging.

Expected result:

Go to a URL that invokes Greaselion. Get some diagnostic logging.

Reproduces how often:

100%

Brave version (brave://version info)

1.19.21

Version/Channel Information:

• Can you reproduce this issue with the current release? yes
• Can you reproduce this issue with the beta channel? yes
• Can you reproduce this issue with the nightly channel? yes

Other Additional Information:

• Does the issue resolve itself when disabling Brave Shields? no
• Does the issue resolve itself when disabling Brave Rewards? no
• Is the issue reproducible on the latest version of Chrome? yes

Miscellaneous Information:

N/A