Add Authentication and Authorization for feast serving

[jmelinav]

What this PR does / why we need it:
PR enables authentication and authorization for feast serving, configurations remain same as feast core's authentication and authorization configuration.
Which issue(s) this PR fixes:

Fixes #823

Does this PR introduce a user-facing change?:Yes

The following params on python sdk "Client" object has been renamed. 
params "core_enable_auth", "core_auth_provider" and "core_auth_token" 
has been renamed to "enable_auth", "auth_provider" and "auth_token" respectively. 
Now same params are used for enabling auth on both core and serving connections.

It doesn't break if auth is enabled only on core and not on serving. 
However client will pass the auth metadata to serving as well.

action required : If deployment has auth enabled, 
then python sdk "Client" object references should be updated to use new params. 

[feast-ci-bot]

Hi @jmelinav. Thanks for your PR.

I'm waiting for a feast-dev member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jmelinav]

/assign @pyalex

[dr3s]

/lgtm

[dr3s]

/ok-to-test

[jmelinav]

/test test-end-to-end-auth

[jmelinav]

/test test-end-to-end-batch

[jmelinav]

/test test-end-to-end-auth

[jmelinav]

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

[feast-ci-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dr3s, jmelinav
To complete the pull request process, please assign pyalex
You can assign the PR to them by writing /assign @pyalex in a comment when ready.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[dr3s]

/test-end-to-end

[dr3s]

/retest

[jmelinav]

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

[dr3s]

/lgtm

[feast-ci-bot]

New changes are detected. LGTM label has been removed.

[feast-ci-bot]

@jmelinav: The following test failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
test-end-to-end-batch-dataflow	aae07e5	link	/test test-end-to-end-batch-dataflow

Full PR test history

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[dr3s]

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