code re-organization before add awe-proxy: making controllers' code shared by proxy and server
code reorg: move server util to common lib
code re-org: move shared packages under AWE/lib
rename AWE/utils to AWE/scripts
code restruct: unify medium workunit struct passed along between workers
rename worker to processor (worker will be used as general client side function unit)
code re-org: mv workers from under awe-client to lib/workers
import update for workers
import updates for logger and util
add event.go for last commit
rename scripts back to utils (not to change documents)
split qmgr methods for reusing and overriding by proxymgr and servermgr; used Go struct embedding
distinguish proxy and server when printing config info
distinguish proxy and server when showing resource type by API
awe-proxy can start workers serving as a client
add client field 'proxy bool' to distringuish proxy as a client to the regular client
awe-proxy can resubmit checked-out workunits to proxy queue
proxy can relay workunit done/fail notification from client to server
code-reorg: mv lib/util/util.go under lib/controller
delete clientprofile.json