Site Logo: Updates site-logo-control-rtl.css using autortl

[creativecoder]

Changes proposed in this Pull Request:

The site logo module is shared between Jetpack and wpcom, but is not synced automatically.

I recently updated wpcom code to bring it into sync with Jetpack (D33102-code). One file that I could not update was site-logo-control-rtl.css, because it is automatically generated by autortl. This PR updates that file in Jetpack with the autortl generated version.

Is this a new feature or does it add/remove features to an existing part of Jetpack?

• See p9dueE-114-p2 for context about the site logo module

Testing instructions:

• Install and activate a theme that supports Jetpack's site-logo, such as Canape
• Go to Settings > General in wp-admin and change the site language to an rtl language, such as Arabic
• Load the customizer and select the "Site Identity" section (first one)
• See that the site logo Customizer control is correctly aligned on the right side of the screen.

Proposed changelog entry for your changes:

• Updated rtl css for site logo module using autortl

[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 🤖

Generated by 🚫 dangerJS against d537f5a

[jeherve]

This is not necessary in Jetpack, as the RTL and minified stylesheets are automatically generated when the built version of Jetpack is created before a release. As a result, your changes would be reverted before the next release.

I did, however, see that the RTL and minified versions were not enqueued when necessary. I created #13654 to fix that.

[creativecoder]

I did, however, see that the RTL and minified versions were not enqueued when necessary. I created #13654 to fix that.

Thanks!