Double user lookup (middleware and service functions)

[BCerki]

Blocked by #827
###Description of the Tech Debt###

For maximum separation between the API and service layer, we pass service functions the user_guid. If we need the full user record, we look it up in the service function. However, we already have the full user record from the middleware when we call the function. This means we look up the user twice, once in the middleware and once in the service function. This ticket is about determining if we should pass the full user record to the service functions to improve performance.

###Tech Debt Triage#
The purpose of our technical debt triage process is to analyze technical debt to determine risk level of the technical debt and the value in tackling that technical debt.

Risk Value Scoring:

Level	Value
High	3
Medium	2
Low	1

Technical Debt - Risk Types	Level	Value
Business Area Risk - Risk of business area visibility / damage to user experience
Developer Fault Risk - How likely will this tech debt cause a future error related to coding on top of it
System Fault Risk - Risk of system errors or application downtime
Time Scale Risk - Compound risk effect if left alone. How much more difficult to fix or dangerous will this become over time?
Time Sink Risk - How much will this tech debt slow the development process down
TOTAL SCORE: