WiP - Kubernetes support

[koszti]

Problem

PipelineWise hardly can run on Kubernetes because of several reasons and primarily because it was not designed with kubernetes in mind.

Proposed changes

This PR is work in progress and will add more commits until it doesn't have everything from the list:

• Add metadata database
• Add scheduler
• Add API with endpoints:
  • GET: /api/v1/health (standard health endpoint)
  • POST: /api/v1/import (for git-sync webhook)
• Add helm charts
• Tests

Expected kubernetes layout:

Types of changes

What types of changes does your code introduce to PipelineWise?

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

• I have read the CONTRIBUTING doc
• Description above provides context of the change
• I have added tests that prove my fix is effective or that my feature works
• Unit tests for changes (not needed for documentation changes)
• CI checks pass with my changes
• Bumping version in setup.py is an individual PR and not mixed with feature or bugfix PRs
• Commit message/PR title starts with [AP-NNNN] (if applicable. AP-NNNN = JIRA ID)
• Branch name starts with AP-NNN (if applicable. AP-NNN = JIRA ID)
• Commits follow "How to write a good git commit message"
• Relevant documentation is updated including usage instructions