/read/match doesnt need user_type

[branden-jones]

If each profile has the aforementioned properties ( see issue #287 ) then this is an already established endpoint that can be used but only...

IF we remove user_type ( preferred and recommended )

OR role is implemented within Profile Object ( but user_type seems to still be redundant and unnecessary )

Having the ability to quickly grab a single object or a simple array of objects cuts down on sorting and looping times as well as smaller amounts of data.