Most of the standard use-agent strings can be parsed into human-understandable information. For instance, the user-agent string `Mozilla/5.0 (Windows NT 10.0; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0` indicates that the user is using Firefox version 55.0 on a computer with the 64-bit version of Windows 10. Some of the other parts (such as rv:55.0, Gecko/20100101=== Goal
**User story**: //As a user, etc) typically give no additional information for the purposes of CheckUser, and we learn to ignore them.it would be helpful if I could see a human-readable version of the User-agent string in the CheckUser interface so that I could easily see which OSs and browsers a user is using.//
We should createOften standard use-agent strings can be parsed into human-understandable information. For instance, `Mozilla/5.0 (Windows NT 10.0; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0` indicates that the user is using Firefox version 55.0 on a computer with the 64-bit version of Windows 10. Some of the other parts (such as rv:55.0, Gecko/20100101, etc) typically give no additional information for the purposes of CheckUser, and can be ignored.
We should investigate having a user-agent parser (similar to what http://www.useragentstring.com/ does), that would show these basic human-understandable information to make it easier to interpret the UAs.
=== Acceptance criteria
* Given a UA string, that would show these basic human-understandable information ***in addition to*** the user-agent stringsplit it into OS and browser
* Display the parsed information
** Add option to see complete UA if needed (mock tbd)
* If the UA is non-standard and cannot be split, to make it easier to interpret thdisplay complete UAs.