Inconsistent behavior in handling Upload New Version in different mimetype between Cloud vs On Prem Share

This is related to MNT-10987. Currently, the mimetype does not update automatically upon new version update in 5.0.1.5 and 4.2.4, and I noticed this behavior is not consistent with latest Cloud UI behavior in my further testing against Alfresco Cloud running Alfresco Cloud v5.0.0 (39.6.3Cloud r111565-b13) schema 8009.

Steps to replicate

1. On fresh vanilla v4.2.4/5.0.1, login to Alfresco Share (http://localhost:8080/share) and upload a Word document (.docx) to any Share site.
2. Use "Upload New Version" to upload a new version (v1.1) of the word document but select a file in PDF format this time.
   • Actual result: You will see that under Properties > Mimetype value remains display as Microsoft Word 2007 and does not update to Adobe PDF Document. You will also see that the "Edit Online" action link is still available but now produces an error message when using the function. Also, the document preview does not generate correctly.
   • Expected result: You will see that under Properties > Mimetype value detect the mimetype change and update to Adobe PDF Document. Edit Online button no longer display. Document preview of the PDF file generated correctly.
3. Open a new browser tab, navigate to Alfresco Cloud (https://my.alfresco.com/share), upload a Word document (.docx) to any Cloud site.
4. Use "Upload New Version" to upload a new version (v1.1) of the word document but select a file in PDF format this time.
   • Actual result: You will see that under Properties > Mimetype value detect the mimetype change and update to Adobe PDF Document. "Edit in Microsoft Office" action link no longer display. Document preview of the PDF file generated correctly.
   • Expected result: You will see that under Properties > Mimetype value detect the mimetype change and update to Adobe PDF Document. "Edit in Microsoft Office" action link no longer display. Document preview of the PDF file generated correctly.

Additional Note:
Customer understand AOS will not work with PDF, they just point it out as it is causing end user confusion, but from the previous test the issue seems to be handling correctly in Alfresco Cloud UI running. Have this issue been fixed in upcoming 5.0.2 as well ?