Use real UUID for obfuscating username

[yli-sugarcrm]

Closes #215

[rhoggSugarcrm]

Thanks a bunch for your first PR to Thorn @yli-sugarcrm!

Left some nitpicky comments, but otherwise looks great!

Please send back to me when you've addressed these.

[rhoggSugarcrm]

Please place a trailing comma at the end of this line.

For future reference, you can run gulp lint before submitting a PR to make sure your code is style-guide compliant.

[rhoggSugarcrm]

We can delete any {1}'s as they're redundant.

[rhoggSugarcrm]

For clarification: the 89AB is the variant part of the RFC 4122 UUID. Per the spec:

Msb0  Msb1  Msb2  Description
    0     x     x    Reserved, NCS backward compatibility.
    1     0     x    The variant specified in this document.
    1     1     0    Reserved, Microsoft Corporation backward compatibility
    1     1     1    Reserved for future definition.

8, 9, A, and B are the only hexadecimal digits that start with 10 in binary; anything higher than that starts with 11 and anything lower than that starts with 01 or 00.

[coveralls]

Coverage increased (+0.01%) to 95.977% when pulling 6546ce9 on yli-sugarcrm:uuid-username-suffix into 895c508 on sugarcrm:master.

Yuyi addressed my comments

[rhoggSugarcrm]

Thanks @yli-sugarcrm!

[jcsmorais]

Username have a maximum length of 60 chars, if we're now using UUID's (which take more than half-of that, 36 chars) should we add something to the documentation to explicitly say these should be under 24 chars?

[coveralls]

Coverage increased (+0.01%) to 95.977% when pulling 41c9502 on yli-sugarcrm:uuid-username-suffix into 9a43d47 on sugarcrm:master.