Ticket 47395 47397 v2 correct behaviour of account policy if only stateattr
	is configured or no alternate attr is configured

Bug Description:  The tickets relate to two specific configurations of
	the account policy plugin
	1] if createtimestamp is configured as stateattr it is treated like a
	   normal timstamp attribute and is updated, which should not happen.
	   As a side effect the account is not locked out based on the original
	   createtimestamp
	2] if no altstateattr is configured, always createtimestamp is used, but
	   the intention was to base account inactivation only on lastlogintime

Fix Description:   1] prevent update of createtimestamp, even if used as stateattr
		   2] if no altstateattr is configured still use the default, but
		      accept "1.1" as null value and check only stateattr

https://fedorahosted.org/389/ticket/47395
https://fedorahosted.org/389/ticket/47397

Reviewed by: ?
Ticket 47329 - Improve slapi_back_transaction_begin() return code when transactions are not available

    Bug Description:  The slapi_back_transaction_begin() function needs it's return codes
                      to be changed to be more friendly for plug-in writers when
                      transactions are not available.

    Fix Description:  Added new error code SLAPI_BACK_TRANSACTION_NOT_SUPPORTED, and
                      updated the slapi_plugin.h

    https://fedorahosted.org/389/ticket/47329

    Reviewed by: Noriko, Ludwig, and Rich(Thanks!!!)