Use blog token to request the jetpack.updateBlog XMLRPC endpoint

[leogermani]

This PR changes the token used by the stats module to make a request to the updateBlog XMLRPC endpoint. It drops the use of the "Master user" token and uses the blog token instead.

Jetpack product discussion

p9dueE-1Dv-p2#comment-2838

Does this pull request change what data or activity we track or use?

No

Testing instructions:

• Open modules/stats.php file

• At line 25 change the STATS_VERSIONvalue to a higher number, for example:
  define( 'STATS_VERSION', '10' );

• This will force a call to the updateBlog endpoint

• Browse the admin panel. Just viewing a page is enough

• Check the stats_options option on the cache site and confirm the value for the version option key was updated :)

• Now revert the change.

• Undo the change to the constant value in the stats.php file.

• On your local environment:

wp shell
$options = get_option( 'stats_options' );
unset($options['version']);
update_option( 'stats_options', $options );

• Visit the dashboard
• Check tha value of the option in the cache site is back to normal

Proposed changelog entry for your changes:

• Use blog token to request the jetpack.updateBlog XMLRPC endpoint

[test-case-reminder]

Here are some suggested test cases for this PR.

Stats

• Visit home page, make sure that page view is recorded in stats
• Visit home page in AMP view
• Visit post page in non-AMP and AMP view

If you think that suggestions should be improved please edit the configuration file here. You can also modify/add test-suites to be used in the configuration file.

[jetpackbot]

	Warnings
⚠️	The PR is missing at least one [Status] label. Suggestions: [Status] In Progress, [Status] Needs Review

This is an automated check which relies on PULL_REQUEST_TEMPLATE. We encourage you to follow that template as it helps Jetpack maintainers do their job. If you think 'Testing instructions' or 'Proposed changelog entry' are not needed for your PR - please explain why you think so. Thanks for cooperation 🤖

E2E results is available here (for debugging purposes): https://jetpack-e2e-dashboard.herokuapp.com/pr-16698

Generated by 🚫 dangerJS against f4b64de

[fgiannar]

LGTM 👍