Update Aztec-Android for alignment handling

[mchowning]

Description

Enables alignment on Android for non <p>-based blocks. In particular,

1. Enables alignment for Heading blocks on Android (was already working on iOS);
2. Applies center alignment for the Pullquote block on Android (was already working on iOS) Pullquote block #1854; and
3. Enables alignment for the Verse block (the option was there before, but it didn't work) Enable alignment toolbar for verse block #2037;
4. Enables alignment for the quote block on both platforms (alignment button was present, and it would update the HTML, but visually the block did not display the selected alignment) Quote Block display does not respect alignment #2161

⚠️ Once the AztecEditor-Android PR is merged, the aztecVersion in this PR must be updated before this is merged.

Related PRs

wordpress-mobile/AztecEditor-Android#899
WordPress/gutenberg#21803
wordpress-mobile/WordPress-Android#11752

Testing

These tests should all be performed on both iOS and Android.

Heading, Verse, and Quote Blocks

[Heading, Verse, Quote].forEach { block ->

1. Select a ^block^
2. Change the alignment for the block
3. Observe the text visually updates to reflect the new alignment
4. Verify that the HTML is updated with the new alignment

}

Pullquote Block

1. Verify that the text in the Pullquote block has center alignment

Regressions

Verify that:

• Alignment still works on Paragraph blocks
• Image and video captions are still centrally aligned

PR submission checklist

• I have considered adding unit tests where possible.
• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

[marecar3]

We're freezing 1.24.0 today. If you think it is ready and if you'd like to ship it with 1.24.0please merge it into develop branch. Otherwise, we can bump it to 1.25.0. @mchowning

[SergioEstevao]

@mchowning I still have hopes that you can have this available on 1.25, but if not please move it to the 1.26 milestone.

[pinarol]

I am changing the milestone of this PR as 1.27 because the 1.26 release branch will be cut quite soon. Let me know if you instead wanted to include this to 1.26.

[hypest]

Looking good code-wise! I still haven't made a pass to test the behavior but I'll LGTM this and someone (or me) can do the testing pass.