Added implementation of getNewExtendMembership(Vo, loa)
Create new attributes for synchronization information about group

- create new module for existing attribute synchronizationEnabled,
  testing value (true, false or null)
- create new module for new attribute lastSynchronizationState, no check
  needed, only information about attribute
- create new module for new attribute lastSynchronizationTimestamp,
  check if timestamp is in correct format
- use new attributes in GroupSynchronizerThread in GroupsManagerBlImpl,
  method run, try to save information about synchronization of this
  group
- create new method saveInformationAboutGroupSynchronization in
  GroupsManagerBlImpl running in the new transaction (use in
  GroupSynchronizerThread)

------------------------------------------
IMPORTANT: Need to do after merging this commit

1] create two new attributeDefinitions
 - urn_perun_group_attribute_def_def_lastSynchronizationState
 - urn_perun_group_attribute_def_def_lastSynchronizationTimestamp
2] set rights for these two attributeDefinitions
3] add these information to the changeLog
Documentation added and fixed

- javadoc fixes in AttributesManager and AttributesManagerBl
- documentation added and fixed in rpc, AttributesManagerMethod
Updated readme files

- Added readme for perun-rpc
- Updated readme for services and DB
Functions for alternative password

  - create alternative password
  - delete alternative password
  - manage alternative password (create and delete work with this
    method)
  - using attribute user:def:altPassword:namespace

----------------------------------------------------
NEED TO DO AFTER MERGING:
1] create new attributeDefinition user:def:altPassword:* (all
possible login namespaces)
2] set rights for this attribute
3] add these information to the changelog!!!
GUI: Do not check for similar users also for vo extension and group

- Disabled check also on auto-approve.
Merge pull request #442 from stavamichal/alternativePassword_fromSlava

Functions for alternative password
RPC: new methods for alternative password

- create alternative password
- delete alternative password
Merge pull request #448 from zlamalp/application

GUI: Do not check for similar users also for vo extension and group
CORE: fixed attribute initialization

- Fixed name of lastSynchronizationState attribute.
- Fixed insert for attributes to handle also displayName
Merge pull request #449 from zlamalp/fixup

CORE: fixed attribute initialization
GUI: fixed check for similar users

- Do not display notice, when no similar users found.
REGISTRAR,RPC,GUI: Check for similar users before app submission

- Check for similar users using federated data or certificate (name/mail).
- Check is performed before submission.
Merge pull request #450 from zlamalp/fixup

GUI: fixed check for similar users
Do not run consolidator if userExtSource is known

If users goes throung chain applications form (for VO and then for group),
then after submiting application for VO the new user is created, but the
perunSession isn't refreshed, therefore checkForSimilarUsers found newly
created user.

This commit fix checkForSimilarUsers. It return no match, if it found
user base on extSource and extLogin from session.
Authz: VoObserver can call getVos
Merge pull request #420 from stavamichal/informationAboutGroupSynchronization

Create new attributes for synchronization information about group

- create new module for existing attribute synchronizationEnabled, testing value (true, false or null)
- create new module for new attribute lastSynchronizationState, no check needed, only information about attribute
- create new module for new attribute lastSynchronizationTimestamp, check if timestamp is in correct format
- use new attributes in GroupSynchronizerThread in GroupsManagerBlImpl, method run, try to save information about synchronization of this group
- create new method saveInformationAboutGroupSynchronization in GroupsManagerBlImpl running in the new transaction (use in GroupSynchronizerThread)
REGISTRAR: do not offer joining identities when user is known

- Backported and modified change from upstream/productionElixirFix.
  When checking for similar users, if user is known (by session or
  actor/extSource) we don't have to offer joining, since perun will
  join application on approval.

  Case when user is known by actor/extSource but not session is when
  user entry was created by previous application with auto-approval
  but session was not updated in GUI (linked app forms).

  Original version returned "no match" for any unknown user, which is not good.
  Check is not performed for non-authz users on GUI side, but this logic
  must be kept in registrar for users with federated identities which we can join
  and which might be found by name or email.
Documentation fix
parm fix in rpc

- removeAlsoUserFacilityAttributes changed to workWithUserAttributes