--rewards=staging=false command-line arg and official builds should use production Ads Serve

[tmancey]

--rewards=staging=false command-line arg and official builds should use production Ads Serve

Steps to Reproduce

1. Launch browser with --rewards=staging=false or an official build

Actual result:

https://ads-server.bravesoftware.com is used for all communications with the Ads Serve for production

Expected result:

https://ads-server.brave.com should be used for all communications with the Ads Serve for production

Reproduces how often:

Easily reproduced

Brave version (brave://version info)

0.63.x

Reproducible on current release:

No

Website problems only:

• Does the issue resolve itself when disabling Brave Shields? N/A
• Is the issue reproducible on the latest version of Chrome? N/A

Additional Information

Ads Serve URL can be seen in the console log

[srirambv]

Verification passed on

Brave	0.63.31 Chromium: 73.0.3683.75 (Official Build) beta(64-bit)
Revision	909ee014fcea6828f9a610e6716145bc0b3ebf4a-refs/branch-heads/3683@{#803}
OS	Linux

• Verfied console logs, request/response uses https://ads-server.brave.com

Verification passed on

Brave	0.63.40 Chromium: 74.0.3729.61 (Official Build) beta (64-bit)
Revision	5df2c8936783bd7575987e45d72a92fcf528496b-refs/branch-heads/3729@{#645}
OS	Windows 10 OS Build 17134.523

• Verified chrome_debug.log, request/response uses https://ads-server.brave.com

Verified passed with

Brave	0.63.44 Chromium: 74.0.3729.75 (Official Build) beta(64-bit)
Revision	fdb7915642fef8cf997beac2554709d148e3c187-refs/branch-heads/3729@{#754}
OS	Mac OS X

• Verified console logs, request/response uses https://ads-serve.brave.com