Indexer-core-plus service

Creation of new indexer-core-plus for Community Implementation.

(Work in progress, not ready to merge.)

Type of change

•  Initial commit (a change for the initial development of a project)
•  Refactor (a non-breaking change that improves code maintainability).
•  Bugfix (a non-breaking change that solves an issue).
•  Dependencies upgrade (a version change upgrade for release management)
•  Enhancement (a change on the existing code, increasing the efficiency or effectiveness of the software without necessarily introducing new features to end user, can include approved ADR)
•  New feature (a non-breaking change that adds functionality, must include approved ADR).
•  Breaking change (a change that is not backward-compatible and/or changes current functionality, must include approved ADR).
•  Deprecation (a change for code deprecation, will need to include this in the release notes)
•  DevOps (a change for CICD related / DevOps for release management)
•  Documentation (a change of documention only)
•  Logging (a change for work related to internal audit, logging, reporting improvement)
•  FOSSA Notice (a change for FOSSA notice update)
•  Revert (a change for reverting a previous MR)
•  Testing (a changes for improving unit, integration, etc. testing)

Please provide link to gitlab issue or ADR(Architecture Decision Record) 

Refactor indexer-gc (#13) · Issues · OSDU Forum / OSDU Project Management Committee - PMC / Community Implementation · GitLab (opengroup.org)

Does this introduce a change in the common core logic?

• [YES/NO]

Does this introduce a change in the cloud provider implementation, if so which cloud?

•  AWS
•  Azure
•  GCP
•  IBM

What is the current behavior?

What is the new/expected behavior?

Have you added/updated Unit Tests and Integration Tests?

Any other useful information