DB: Updated DB version in sql files comments to current
Merge pull request #586 from zlamalp/db

DB: Updated DB version in sql files comments to current
New Synchronizer workflow

 - synchronizer will synchronize only those extSource members with
   correct informations and attributes
 - method getCandidate from extSource and login will change firstName
   and lastName on null if in not correct format
 - methods createMember* will throw WrongAttributeValueException and
   WrongReferenceAttributeValueException instead of consistency
   exception, because this is not the same
 - new ParserException created for parser errors in Perun
 - method synchronizeGroup will return List<String> with info about skipped
   members and the reason why were skipped
 - method synchronizeGroups will set exception to attribute for this
   purpose to inform user about skipped extSource's members
 - when some problem occurs (like parserException,
   attributeValueException, candidateNotExistsException) in
   synchronization, member of extSource which create this exception will
   be skipped and information about this skipping will be add to
   attribute with info about last synchronization of group
Merge pull request #583 from stavamichal/newSynchronizerWorkflow

New Synchronizer workflow
New method of date comparison in synchronizer

Fix of c5a83c75cc749b5d33dfc1cac4426d52ae18a161

Old method for comparing dates do not work properly (sadly I don't have
enough time to find cause).
Revert "make engine ignore facilities (for testing of new engine)"

This reverts commit 5876305d5eaae3c210beed7d08567038c98d520a.

This commit should not get to master branch.
Fix of typo in synchronize

 - fix of type when concating strings (need to use += instead of =)
Merge pull request #588 from stavamichal/synchronizationWorkflowFix

Fix of typo in synchronize
nested transaction for createMemberSync

Nested transaction for membersManagerBl().createMemberSync

It fixes problem caused by 09add5b4748d229187b30d27f75008b65fec5094
(New Synchronizer workflow) - There is caught exception from
createMemberSync wich is not throw out. Therefore there is no rollback
and by that the inconsistency in database is made (member is created but
he is not in members group).
Add fix to get correct information about group Synchronization

 - attribute has only 4000 char limitation so we need to save only
   messages with less than 4000 char (default will be on 3000 for save),
   other information need to be write to log.
Merge pull request #589 from stavamichal/fixSavingSynchronizationStatus

Add fix to get correct information about group Synchronization
CORE: Fixed type of returned exception for LoA

- When member is checked for possible extension and fails,
  we must return INSUFFICIENTLOAFOREXTENSION type of exception,
  so GUI will perform redirect.

  There originally was INSUFFICIENTLOA which is case only when user
  is not yet member of VO.

- Added javadoc for methods canBeMemberInternal(), manageMembershipExpiration().
CORE: Do not allow members with insufficient loa

- When creating member, check if he/she can be member by loa
  and vo membership expiration rules.

  If not - throw an exception which will rollback creation.

- Fixed test for membership extension, which must assert against
  INSUFFICIENTLOAFOREXTENSION.
CORE: skip member creation when can't set membership expiration on sync

- Skip creation of member on synchronization of group when
  we can't properly set membership expiration based on VO's rules.