Conflictvisualizer api integration

[jacob6838]

PR Details

Description

Adding the JPO-ConflictVisualizer API to the cvmanager services directory. This is a Java Spring-Boot api.
These changes are built off of the Feature/intersection-tables PR.

** Note**
When pulling this branch, you may have to enable long file paths in git:

git config --system core.longpaths true

This process is further defined in services/conflictvisualizer-api/README.md

How Has This Been Tested?

This was tested using the docker-compose.yml, after commending in the local image and build tags

Types of changes

• Defect fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that cause existing functionality to change)

Checklist:

• My changes require new environment variables:
  • I have updated the docker-compose, K8s YAML, and all dependent deployment configuration files.
• My changes require updates to the documentation:
  • I have updated the documentation accordingly.
• My changes require updates and/or additions to the unit tests:
  • I have modified/added tests to cover my changes.
• All existing tests pass.

[John-Wiens]

Do we want to continue to call the conflictvisualizer-api the conflictvisualizer-api? If all goes to plan the conflict visualizer won't really exist a year from now, so maybe best to rename it now.

[John-Wiens]

The Conflict Monitor is now a submodule of the CV Manager. Should the references to the Conflictmonitor/connect context should be updated to point to the Conflict Monitor Connect context within the submodule.

[jacob6838]

I can add some optional comments for this, but think 99% of the time the pre-built image should be fine. Faster build times and less changes for build errors

[John-Wiens]

Should this be deleted, and the version inside of the conflict monitor submodule be used instead?

[jacob6838]

good call, yup!