D-Net

[Trunk | Claims Service]:
1. ManagerUtils.java: [NEW] File for getting community managers from registry service added.
2. springContext-claims.properties: Property "services.claims.registryAPIForManagerEmails" added - URL of registry service for requesting community manager emails....

Updates to Migrate community claims from Beta to Production

CommunityUtils:
chnage methods from static, add it with autowired in EmailSender
update properties

Update email Sender and Scheduler:

rename property emailScheduler.sendEmailNotifications to services.claims.mail.sendEmailNotifications

Add properties to enable/disable notifications for specific entities:
services.claims.mail.notifyCommunityManagers
services.claims.mail.notifyProjectManagers

Fix1: set type after parsing response from external sources - this fix puts the record in the proper file path

Fix2: Update orcid parser, use single orcid work response
update ExternalParserTest

ClaimEntity: Add information about the dashboard where the claim was created

Properties:
add properties for the different services
create beans properly
production or beta is decided from the services urls in properties

Migration:
create migration method: CopyFromBetaToProduction for communities

Search utils, Project Handler, IndexResultHandler:
get search service url from properties
remove isProduction parameter
remove dedup result methods used in migration

-> update method calls and signatures accordingly

- rename properties files springContext-claimsDemo.xml --> springContext-claims.xml
- rename properties paths services.claimsDemo.* to services.claims.*

-Remove methods and classes used for the migration from old database schema to new
-Remove communities XMLs
-rearrange packages (remove 'migration' and 'claimsDemo') Properties paths didn't change!

springContext-claimsDemo.properties: Property 'sendEmailNotifications' set to false by default.