Add synchronizeGroup to nested transaction
New behavior for creating and calling auditerConsumer for LDAP

CORE,RPC,RPC-LIB:
- change behavior of method pollConsumerMessagesForParserLikePairWithId,
  return List<auditMessage> instead of List<Pair<String,Integer>>
- change name of methods pollConsumerMessages* to be more simple
- fix bug in Auditer.java (using bad variable lastProcessedId)
- add mehotd pollConsumerMessagesForParser to RPC-LIB
- remove AUDITER_LOG_MAPPER_FOR_PARSER_WITH_ID from Auditer (not needed now)

LDAPc:
- remove datasource from ldap (using rpc now)
- remove perun-ldapc-applicationcontext-jdbc.xml (not needed now)
- remove bad autowiring variable ldapcManager in LdapcStarter
- add @org.springframework.stereotype.Service to
  EventProcessorImpl
- use method pollConsumerMessagesForParser in LDAP EventProcessorImpl,
  reading messages by RPC through RPC-LIB

Tested on localhost
Merge pull request #395 from stavamichal/newCallingAuditerForLDAPFromRPC

New behavior for creating and calling auditerConsumer for LDAP
Merge pull request #384 from stavamichal/synchronizerInTransaction

Add synchronizeGroup to nested transaction
Fix delay of forcePropagation methods

forcePropagation methods uses audit message to notify engine about force
propagation request. Ussually, audit messages are stored to current
thread and waiting for commit of DB transaction; in this case there are
no queries in DB transaction, therefore the audit meessages are stuck
and waiting for commit of next DB transaction. (Not sure, where exactly
the messages are stuck).

This commit fix this behaviour by setting forcePropagation methods to
store audit messages to DB aside from DB transaction.

Details:
- create new method logWithoutTransaction
- storeMsgToDb method do not run in transaction
- call method logWithoutTransaction in forcePropagation methods

Original author: Michal Stava <stava.michal@gmail.com>
Modifications of decsriptions: Slavek Licehammer <slavek@ics.muni.cz>