Comment Detail: Fix content cell elements not resizing in AX size

[dvdchr]

Refs #17087

As titled, this PR now ensures that:

• The content cell header properly displays the text under increased font size.
• The Reply and Like buttons' sizes are adjusted along with the device's font size.

---

⚠️ Auto-merge is enabled. ⚠️

---

To note: I've tried to fix an issue with VoiceOver but to no avail. The screen reader somehow jumps to the top of the screen again after reading the contents of the web view. It looks like WKWebView is buggy (just my luck), and after loading the HTML content, somehow the accessibility parent of the web view got reassigned. I believe this is what caused the screen reader to "jump".

The highlighted element is the table view container. As you can see, there are five elements. The first one is the comment header, the second one is the content cell, and so on. Next is the hierarchy for the content cell:

Above is the content cell element unwrapped. You can see all the accessible elements there in the content cell¹, and the one that I highlighted is a group for the web view. Next, I'll go deeper into the web view and this is what I got:

"Hey there." is the comment content. As you can see, it's somehow nested right under SimulatorKit.SimDisplayRenderableView, which is almost at the very top of the hierarchy. This is why the screen reader won't continue after reading the contents of the web view. Sigh.

I have tried a lot of things to fix this and to the point of accessing the private WKContentView class of WKWebView to see if I could apply some hack or something, but nope. This gives me more reason to create a standalone, reproducible project and submit a radar. 😅

To test

• Increase device/simulator font size.
• Enable newCommentDetail feature flag.
• Go to My Site > Comments and select any comment.
• 🔍 Verify that the content cell is displayed correctly, adjusting the contents' sizes with the device's current font size.

Regression Notes

1. Potential unintended areas of impact
   n/a. Feature is unreleased.

2. What I did to test those areas of impact (or what existing automated tests I relied on)
   n/a. Feature is unreleased.

3. What automated tests I added (or what prevented me from doing so)
   n/a. Feature is unreleased.

PR submission checklist:

• I have completed the Regression Notes.
• I have considered adding unit tests for my changes.
• I have considered adding accessibility improvements for my changes.
• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

Footnotes

1. There's also a strange ordering issue here. Somehow the web view element is placed after the Reply and Like button. 🤔 ↩

[peril-wordpress-mobile]

You can trigger an installable build for these changes by visiting CircleCI here.

[peril-wordpress-mobile]

You can trigger optional UI/connected tests for these changes by visiting CircleCI here.

[ScoutHarris]

With large text (in this case, Accessibility Medium) it looks like the label stack view isn't growing properly. Sometimes the name is cut off, sometimes the date is.

I'll go ahead and approve (disabling auto-merge) so it can be fixed and merged to make the release. Or if you like, it can fixed separately and this can just be merged.

[dvdchr]

With large text (in this case, Accessibility Medium) it looks like the label stack view isn't growing properly.

Thank you for noticing this @ScoutHarris !! I swear I've had this fixed yesterday 😅. Oh well. This should now be addressed in c3d47ec. Here are some screenshots:

Normal	AX Medium	AX Large