frontend: Fix resources bug

Now rpc_utils.create_new_job() takes a profile argument,
so we have to pass it through. This fixes the resources
unittest.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
base_syncdata_unittest: Remove bad unittest

This is the actual solution for issue #296.

The unittest with a fake server (that in fact is not
really fake, it's the barrier listen server) was
creating a rogue, paused process at the end of this
unittest run. As it uses base barrier server, it
will cause the barrier unittest to fail the next
time you run the unittests, since this process is
there holding up the barrier ports.

CC: Vinson Lee <vlee@twitter.com>
CC: Jiri Zupka <jzupka@redhat.com>
Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>
unittest_suite: Put base_syncdata_unittest in the long runtime tests

The SyncData unittests take even longer than barrier,
and should be in the long runtime test list. This way
we keep the 'quick' unittests really quick.

Signed-off-by: Lucas Meneghel Rodrigues <lmr@redhat.com>