Move XML based Spring configuration to Java

- The original externalised Spring XML-based configuration deployed to:
    /opt/app/spike-service/dynamic/conf/spike-beans.xml
  has been replaced with Spring Java based configuration.
- Event consumer and publisher configuration is now in property files.
  This now allows obfuscation of passwords.
- Bean creation now allows pre-processing the topic properties.
  For example, the password can now be de-obfuscated before it is
  passed into the bean constructor.

Change-Id: I5c265dca266b0dcbb562ca1b391080fe237b1e64
Issue-ID: AAI-1377
Signed-off-by: Michael Arrastia <MArrasti@amdocs.com>

Migrate Spike code to ONAP

Move what was originally an Open ECOMP microservice into ONAP.
This is primarily a code move and includes:
- removal of AJSC and replacement with latest version of Spring Boot
- alignment with ONAP standards
- license headers
- package renaming
- FOSSology scan completed
Further work is required to add JJB and OOM.

Change-Id: I305c8407256bf2dbcc816f34f031f92eafd6ef5a
Issue-ID: AAI-1374
Signed-off-by: Michael Arrastia <MArrasti@amdocs.com>

Correct INFO.yaml to pass YAML Lint

Change-Id: Ia20bbbc15c51043e4463df104ed42d9eeab8d81d
Issue-ID: AAI-1022
Signed-off-by: Eric Debeau <eric.debeau@orange.com>

Add INFO.yaml file

Add INFO.yaml to list:
- Project description
- Properties
- PTL information
- Meeting information
- Committer information

Change-Id: I2cc4ebb7711bc6763e6e6d125307c8ac7a7573db
Issue-ID: CIMAN-134
Signed-off-by: Jessica Wagantall <jwagantall@linuxfoundation.org>

Initial empty repository