JobCoordinator can be configured to use only subset of FeatureSets or Stores

[pyalex]

What this PR does / why we need it:
This PR adds ability to configure via application properties which FeatureSets and Stores will be available in (and managed by) current instance of JobManager.

This should be useful when you have several deployments of JobManager and each will be responsible for only subset of FeatureSets.

Which issue(s) this PR fixes:

Fixes #

Does this PR introduce a user-facing change?:

# application.yaml
feast:
  jobs:
    coordinator:
      # Specify feature sets that should be handled by current instance of JobManager
      featureSetSelector:
        - project: "*"
          name: "*"
      # Stores names that will be used by current instance of JobManager
      whitelisted-stores: [online, online_cluster, historical]

[pyalex]

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

[pyalex]

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

[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

[woop]

/lgtm

[feast-ci-bot]

New changes are detected. LGTM label has been removed.

[pyalex]

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