Ledger Flags needed for QA

Description

When QA-ing Brave Payments on browser-laptop (muon) there are several flags that we use/have used previously. These flags should be implemented for Brave Rewards to assist with QA.

• LEDGER_NO_DELAY
• LEDGER_NOTIFICATION
• LEDGER_REFERRAL_CHECK_TIME

LEDGER_NO_DELAY was also used, but I believe is not needed since there will not be a 30 minute minimum browsing time requirement for Brave Rewards. If this isn’t true, then we will need this flag as well.

Here is a list of other flags, but not all of them have been used for QA (to date): https://github.com/brave/browser-laptop/wiki/Command-line-flags#environment-variables

cc @brave/legacy_qa for additional input

[LaurenWags]

verbose and env flags are being tracked in a different issue as they were already logged when I discussed this with @NejcZdovc https://github.com/brave-intl/bat-native-ledger/issues/62

[kjozwiak]

@bsclifton I don’t think this should be placed into the 1.x Backlog unless b-c already has built in flags that we can use during ledger/rewards testing.

@NejcZdovc are we going to be using staging servers? If so, how can we use the staging server with b-c? Are we going to need any of the previously created flags to correctly test rewards? If that’s the case, adding flags into b-c when possible is probably a good idea rather then waiting just before the 1.x release.