Run JobCoontroller as separate application

[pyalex]

What this PR does / why we need it:

This is final PR in series of decoupling JobCoordinator (renamed to JobController) from Core.
Main features of PR:

1. There's new module job-controller that should be run as standalone (spring) application (helm charts, docker compose, e2e tests updated)
2. This module communicates with Core through GRPC API. Although job-controller use core in test scope.
3. Ingestion related methods were moved out of CoreService API into JobController API (see CoreService.proto). Since it could be deployed with several instances of JobController - routing between them is now client's responsibility. Also, client code (in python SDK) calling those methods were moved out of Feast Client. Now it's in contrib (see feast.contrib.job_controller.client in python SDK).

Refactoring:

1. Common code for integration tests moved to feast-common-test module

Which issue(s) this PR fixes:

Fixes #

Does this PR introduce a user-facing change?:

Dedicated spring application job-controller
feast.jobs properties moved from core to job-controller

[Deprecated] CoreService.ListIngestJobs, CoreService.RestartIngestJob, CoreService.StopIngestJob

[New API] JobControllerService.ListIngestJobs, JobControllerService.RestartIngestJob, JobControllerService.ListIngestJobs.StopIngestJob

[Python SDK] feast.client.Client.list_ingest_jobs -> feast.contrib.job_controller.client.Client.list_ingest_jobs
[Python SDK] feast.client.Client.restart_ingest_job -> feast.contrib.job_controller.client.Client.restart_ingest_job
[Python SDK] feast.client.Client.stop_ingest_job -> feast.contrib.job_controller.client.Client.stop_ingest_job

[pyalex]

/test test-end-to-end-batch-dataflow

[pyalex]

/test test-end-to-end-redis-cluster

[pyalex]

/test test-end-to-end

[pyalex]

/test test-end-to-end-redis-cluster

[pyalex]

/test test-end-to-end-redis-cluster

[pyalex]

/test test-end-to-end-auth
/test test-end-to-end

[pyalex]

/test test-end-to-end-auth

[pyalex]

/test test-end-to-end-batch

[pyalex]

/test test-end-to-end-batch

[woop]

/lgtm

[pyalex]

/test test-end-to-end-batch

[pyalex]

/test test-end-to-end-batch

[pyalex]

/test test-end-to-end-batch

[pyalex]

/test test-end-to-end-batch

[feast-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pyalex, woop

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [pyalex,woop]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment