Workflow orchestrator for scalable/reliable ingestion

[JayGhiya]

Workflow orchestration has to be enabled for Scalable and reliable ingestion.

[JayGhiya]

@vipinshreyaskumar please create a separate folder in root-repo as of now. Sub folder can cause issues for ci/cd. Root folder could be called unoplat-code-confluence-harvestor if you feel that's a cool name. Second when you start committing please follow https://www.conventionalcommits.org/en/v1.0.0/ as our ci/cd depends on it and it will cause issues if commit messages do not follow the convention.

So I am working on total rewamp for context performance reliability at algorithm level in #206 issue once that's completed we could merge harvestor code and current utility.

[JayGhiya]

• Test it with config file reading local repository when starting up.
  Figure out how to check and not read again the same repository because of docker-compose restart. Otherwise too much tokens could be used up unnecessary.
• Test after reading through archguard activity. Refer Ingestion Utility: All class , func metadata and Func to func call ingestion into Neo4j #206 - Arcguardhandler . This will also give us clarity how to run other programming lang based cli lib inside temporal in best way possible
• Test with temporal nodejs client call for a diff on an sample repository through different diff archguard workflow inside temporal - how does it handle?
  Reference: https://github.com/archguard/archguard/tree/master/scanner_cli