Add #ifdef SMACK_ENABLED to private code.

Add #ifdef SMACK_ENABLED to private code.

With this define commented, all security-server API
should work as if there was no SMACK error and SMACK
allowed for everything.

[Issue#]   SSDWSSP-206 & SSDWSSP-221
[Bug]      N/A
[Cause]    SS should work without SMACK enabled.
[Solution] As mentioned above.

[Verification] Build with and without ADD_DEFINITIONS( -DSMACK_ENABLED ).
1. SMACK enabled system.
1.1 -DSMACK_ENABLED on: SS tests should not fail
1.2 -DSMACK_ENABLED off: Following SS tests should fail:
 -client-smack:
  -tc04_security_server_get_gid_client_is_not_allowed
  -tc05_check_privilege_by_cookie
  -tc06_check_privilege_by_sockfd
  -tc07_check_privilege_by_sockfd
 -label:
  -tc_security_server_get_smacklabel_cookie
 -server:
  -tc01a_security_server_app_give_access
  -tc02_check_privilege_by_pid
 There should be no missing SMACK rules for security server sockets in dmesg

2. SMACK disabled system. Same results for -DSMACK_ENABLED on and off. Beside tests
failing in 1.2 all test cases using smack_accesses_apply and smack_have_access will also fail.

Change-Id: Ia1074d9da4a07e3a60878030b9b8fc3760340c73

Conflicts:

	src/client/security-server-client.c
	src/server/security-server-cookie.c
	src/server/security-server-main.c