MacVim exports standard UTIs, and does it wrongly, messing up the system

Instructions: Replace the template text and remove irrelevant text (including this line)

Describe the bug
MacVim exports standard UTIs, such as com.adobe.postscript. This is wrong, they should be imported, as they are defined by the system. What is worse, the declaration is seriously wrong. It declares the UTI as conforming to to public.plain-text. THIS IS WRONG it should conform to public.data and public.composite-content. This messes up the system seriously. For instance, when an app checks a UTI, it should use conformsTo to do so, and this will match public-plain-text for postscript, breaking the (other!) app. So you are actually sabotaging other apops and the system.

To Reproduce
In an (other!) app, check an UTI (for instance when writing data from a document based cocoa app) against com.adobe.postscript or public.plain-text (if both are supported)

Expected behavior
This should always match com.adobe.postscript when the type is com.adobe.postscript, and should match public.plain-text for public.plain-text.

Actual Behavior
When comparing public.plain-text against com.adobe.postscript, it now matches (conforms to), even if it should not.

Screenshots
If applicable, copy/paste the text or add screenshots to help explain your problem.

Environment (please complete the following information):

• Vim version [e.g. 8.1.1234] (Or paste the result of vim --version.)
• OS: [e.g. Ubuntu 18.04, Windows 10 1809, macOS 10.14]
• Terminal: [e.g. GNOME Terminal, mintty, iTerm2, tmux, GNU screen] (Use GUI if you use the GUI.)

Additional context
Don't ever sabotage the system.

The issue does not name a file or test. Start by locating MacVim's macOS UTI declarations and compare how standard UTIs such as com.adobe.postscript are exported or imported. Done means standard UTIs are not incorrectly declared as conforming to public.plain-text, and the reported conformance comparison no longer matches.